-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hello,
I noticed that for multiple release we have updates which stuck in bodhi for many months until distro goes EOL.
I wonder if we should just auto-unpush updates which are in testing in 1(?) month? Thoughts? - -- - -Igor Gnatenko
On Sat, Jan 13, 2018 at 5:28 AM, Igor Gnatenko < ignatenkobrain@fedoraproject.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hello,
I noticed that for multiple release we have updates which stuck in bodhi for many months until distro goes EOL.
I wonder if we should just auto-unpush updates which are in testing in 1(?) month? Thoughts?
I don't think having them sit in testing hurts anything but my OCD...
I would be in favor of a phased approach to EOL where new updates are stopped a week or two before everything is fully closed so I would have an opportunity to push the ones already in testing to stable.
Thanks, Richard
I don't think having them sit in testing hurts anything but my OCD...
It's a PITA when creating other packages, you don't know if you can target testing state or if it will never be pushed to stable
Regards,
On Sat, 2018-01-13 at 12:28 +0100, Igor Gnatenko wrote:
Hello,
I noticed that for multiple release we have updates which stuck in bodhi for many months until distro goes EOL.
I wonder if we should just auto-unpush updates which are in testing in 1(?) month? Thoughts?
I agree with autopush packages in updates-testing, between mass branch and final release. After GA (general availability), I think is legit have thing in testing. I wrote about this subject some years ago, I'll explain what I thought, in phase of betas some people (like me) may enable update-testing to test more quickly the new fixes and after release they (and I) disable the update-testing which leaves that systems with packages that never hit the stable.
But dnf distro-sync fix this issue ... so maybe isn't a problem .