On Fri, 2009-08-21 at 18:39 +0200, Jaroslav Reznik wrote: > On Friday 21 August 2009 12:08:58 Michal Hlavinka wrote: > > On Tuesday 11 August 2009 16:30:24 Rex Dieter wrote: > > > Fabio Canepa wrote: > > > > Hi, > > > > I've update my F11 to kde 4.3.0 using the following command: > > > > > > > > sudo yum --enablerepo=updates-testing groupupdate 'KDE (K Desktop > > > > Environment)' > > > > > > > > but I'm not sure this is correct way because I've some trouble trying > > > > to test the updates for bug 516386 > > > > > > Fwiw, here's what I posted to the bug, > > > > > > The short version of the answer is: You're pretty much expected to use > > > all of updates-testing for the full QA/testing experience, see also: > > > http://fedoraproject.org/wiki/QA/Updates_Testing > > > > > > In the past, we've occassionally copied all pertinent stuff from > > > updates-testing into kde-redhat's kde-testing repo(s) for targetting > > > testing, and we may end up doing that here, but it hasn't happened yet. > > > > what repo is better for testing kde 4.3? kde-testing or updates-testing? It > > seems kde-testing is better, because there's no need to wait for 'push', > > but for example kdelibs in kde-testing=kdelibs-4.3.0-0.1 vs. > > kdelibs-4.3.0-5 in updates-testing. So only updates-testing should be used? > > Once it's in updates-testing, definitely use it as kde-testing is used to test > stuff before pushing it to updates-testing, prepared manually from first Koji > builds. > > kde repo on sf.net -> updates-testing -> updates... There should be seamless > transition... It's not so clear-cut. See the thread starting at http://lists.fedoraproject.org/pipermail/fedora-kde/2009-August/003616.html poc
