On Fri, 09 Dec 2016 06:07:02 +0100, Kevin Kofler wrote: > However, I also do not see why we cannot just do such big updates through > the regular update process rather than in a big .1 drop. The KDE SIG has > experience with pushing big grouped updates that look a lot like a .1 > release for Plasma users. They go through the regular update process just > fine. Grouping them together with updates to GNOME, LibreOffice etc. in one > batch is not necessary and would only add unnecessary delays. And there it is again, the rush to get out updates. Quickly! Quickly! What has been released before is not bug-free, and the update are not bug-free either, and even if no user has reported a bug, the flow of updates will ensure that the user will be affected by a new bug eventually. If as a maintainer you don't release version upgrades quickly, some users complain everywhere they are permitted to post. Except for bugzilla. And if you make available upgrades quickly, the users will complain if they think they are affected by bugs. Upstream release cycles are not aligned with Fedora's dist release schedule anyway. > I think pushing all updates in a big drop will actually make them LESS > tested than if they just trickle through one at a time. The latter is turning all users of the stable "updates" repo into testers once those updates are unleashed so quickly. And those brave ones, albeit only few, who would be willing to evaluate "Test Updates" for some time, don't get any real chance to do so, because updates are rushed out. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
