Re: New bodhi release in production
On Fri, Aug 13, 2010 at 3:02 AM, Kevin Kofler kevin.kof...@chello.at wrote: Luke Macken wrote: Ok, so the problem here is that bodhi unpushes updates when you edit *anything* in it. If it only unpushed an updated when you add/remove builds from it, then this scenario would be sane. There's still the We've been testing a new KDE release for 2-3 weeks, now we need to edit in a one-line regression fix to one package of the huge group before pushing this to stable. scenario. This has been the case quite often. With your fix, we'd have the choice between pushing the update with a known regression (yuck!!!) or waiting another full week (also quite a bad option). If you have been *testing* it for 2-3 weeks surely you have no problem to find two testers to confirm the small fix? I know you never run kde from updates-testing yourself, so I understand why you think nobody would want to test it. But the reality is that even if you don't want to test your work yourself, there are people who can verify the fix so that the update can go out sooner if need be. M.T. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: New bodhi release in production
On Sat, Aug 14, 2010 at 8:05 PM, Kevin Kofler kevin.kof...@chello.at wrote: Martin Sourada wrote: I still remember the epic fail of having KDE 4.0 in stable fedora * I still think the KDE 4.0.3 we shipped in F9 wasn't that bad. We fixed all the showstoppers before F9 was released, and were also quick to ship updates fixing more annoyances, including updates to later 4.0.x releases. Yes, I used F9 with 4.0.x myself, one one machine. Wow, you actually used F9 yourself (on one machine)? What an accomplishment. * KDE 4.0 wasn't an update at all! It was what was shipped with a NEW release. We intentionally DID NOT update F8 to KDE 4.x. Not 4.0, not 4.1, not ever. This kind of changes is exactly what we have releases for and why rolling release models are not usable for production. * Version updates, the very ones you complain about, brought that 4.0 up to 4.1 and later 4.2. I used F9 on my main machine from F8's EOL up to F9's EOL. F9 with KDE 4.2 (and IMHO even 4.1) was rock solid, actually one of the stablest Fedoras I used. (For example, F10 had issues with my hardware's ALSA driver affecting PulseAudio, F11 with the graphics driver.) Are you seriously trying to say that you updated your own machine to Fedora 9 (KDE 4) 7 (!) months after it was rolled out? I have no words. Good work using everybody else as your test subjects: when they have ironed out all the bugs, you finally update your own computer. M.T. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)
On 03/03/2010 08:38 AM, Kevin Kofler wrote: So maybe you are under the impression that all the users who would test your package are anxiously waiting for your packages to be available? For those packages where regressions actually matter to people, they definitely are. People keep asking us: when will KDE x.y.z finally be available? They ask it even before upstream officially announces the release! Thanks for the concern, Kevin. When will KDE 4.4.2 be available? I've skipped all updates on my mother's computer since you pushed 4.4.0 to updates-stable. With 4.4.2 I might finally consider applying updates again. P.S. If you didn't notice the sarcasm, then I'm not supporting major updates in the so-called stable branches. Such updates are probably fun for people who want to have shiny toys to play with, but some people want to get work done. Using Fedora. List Troll -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
