On 9/3/22 02:58, Mattia Verga via devel wrote:
Il 03/09/22 06:36, Demi Marie Obenour ha scritto:
On 9/2/22 13:49, Mattia Verga via devel wrote:
Here we go again: thunderbird 102 update was submitted to F36.
This new version was known to bring incompatible changes to several addons, yet it has been submitted to a stable Fedora release with autopush enable and just a karma threshold of 2. It took less than 5 hours from the time the update was submitted to the time the update was pushed to stable.
Package maintainers should put more attention when pushing critical updates like this and avoid that the update being immediately pushed to stable.
Thunderbird 91 will go EOL eventually, assuming it has not done so already. As every Thunderbird update bring security fixes it is not possible to guarantee that such an update will not be necessary within the middle of a Fedora release. -- Sincerely, Demi Marie Obenour (she/her/hers)
I do not argue with that, I'm just saying (ranting) that, knowing 102 likely breaks installed addons, it seems to me that at least an announcement on devel list prior to push it into a stable release would have been appreciated.
Moreover, thunderbird in on the critical path update list; Bodhi requires 14 days of testing for those packages, but it is set to require only +2 karma, so packagers easily bypass the testing phase, like it is clearly happened here (pushed to stable just after 5 hours). I think critpath updates should spend more time in testing, maybe we should increase the critpath min karma to, at least, +5.
For non-security, non-kernel, non-browser updates that would make sense. For security patches, anything that makes them take even longer to get to users is a bad idea. This includes kernel and browser patches.