[atomic-wg] Issue #303: Do at least 1-2 more 25 releases, or just switch to /updates
dustymabe added a new comment to an issue you are following: `` we could just have bodhi start updating the 'release' ref instead of the updates ref, but I almost think that's could be misleading as well. At this point it would be good if a decision was made, either decide to stay on f25 (rebase to updates ref), or choose to move to 26 (rebase to 26 remote and 26 ref). We'd obviously need to be more clear on the fact that a decision is required (I'm have a blog post planned to talk about upgrading from f25 to f26, we could talk about this then. WDYT? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/303 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
[atomic-wg] Issue #303: Do at least 1-2 more 25 releases, or just switch to /updates
walters reported a new issue against the project: `atomic-wg` that you are following: `` In https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/ and https://pagure.io/atomic-wg/issue/228 we did some handwaving about releases that IMO was very vague :smile: Now that 26 is out, every 25 AH will simply stop receiving updates without admin intervention (either https://fedoraproject.org/wiki/Atomic_Host_upgrade or `rpm-ostree rebase fedora-atomic/25/x86_64/updates/docker-host`). I really think we need at least some grace period here. Also I'd like some time to polish off end-of-life notification better. So I propose we add infrastructure to continue promotion of /updates -> stable for the 25 ref for at least 2-3 releases. However, we wouldn't release new media (cloud images, ISO) for 25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/303 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
