On Wed, 2014-12-03 at 18:21 +0100, Ralf Corsepius wrote: > On 12/03/2014 05:54 PM, Neal Becker wrote: > > > What is needed here, is an option to yum to use updates-testing _only_ to solve > > broken deps. > > This would be playing with symptoms. What we need is a fix to the Fedora > release process. It simply is broken and has always been broken, ever > since Fedora exists. Nothing's broken. Fedora 21 is not yet released. There's no reasonable expectation that upgrades should work perfectly at this point. An issue like this, which is a perfectly logical and understood consequence of a reasonable release process, does not indicate that 'it simply is broken'. The updates repository is populated before we announce the release. If there are broken upgradepaths at that point we should aim to fix them as a high priority before release. There are logically speaking only two ways you could possibly 'fix' this without introducing yet another repository, if that's what you wanted to do: 1. Implement a perfect and strictly-enforced upgradepath test The consequence of this would be that no-one could update anything in a stable release past the version in Branched stable - *even during a Branched milestone freeze* 2. Implement a perfect and strictly-enforced upgradepath test and abandon milestone freezes The consequence of this would be be we'd probably never manage to get the damn milestone releases done because people would keep pushing changes that break them. Neither of those seems likes an improvement on the current situation to me. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
