On Wed, Nov 14, 2018 at 4:42 PM, John Florian <jflorian@xxxxxxxxxxxxx> wrote:
I still don't understand what makes updating these for a *new* release significantly easier than an *existing* one. So let's just say GNOME (or whatever) comes out next month with a new major release we want to showcase. Why is it necessary to have a Fedora 30 to be able to realize this update. What is so difficult about providing this for Fedora 29. I'm trying to understand why these upstream updates can't be decoupled from the Fedora release schedule.
It's all a matter of QA. The freeze, the blocker bug process, and the quantity of users who test the stuff for us. We'd need major changes to our updates process to account for this in a mid-release update. The blocker bugs process would be needed, for a single bodhi update. At leas
t a month or two of testing (during which new versions of the update will be released, so the update will have to go through some iterations). And lots and lots of testers: currently we get those for free because tons of people help us test beta releases of Fedora, I think far more than run updates-testing.
This is all doable and solvable. Not a blocker. But if we don't take it seriously and make some big changes in how we release updates, it won't go well. Not well at all. So I'd recommend against it, unless there is some major benefit available from doing so.
Michael
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
