#303 Do at least 1-2 more 25 releases, or just switch to /updates

Created 5 months ago by walters
Modified 4 months ago

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.

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?

5 months ago

Metadata Update from @dustymabe:
- Issue tagged with: meeting

In the meeting last week we agreed we could update this so that the release ref gets updated by bodhi every night. Here is a patch sent to infra to make that happen:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/BGJUKGL7UAFQLDXNXFEWKSTN3C743ZYB/

5 months ago

Metadata Update from @dustymabe:
- Issue untagged with: meeting
- Issue assigned to dustymabe
- Issue tagged with: infra

This is done - the f25 release ref will get updated every time bodhi runs now. One side effect is that the updates ref no longer gets updated.

5 months ago

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Fixing the updates ref should literally just be:

ln -sfr 25/refs/heads/fedora-atomic/25/x86_64/{docker-host,updates/docker-host}

I'd like to not set precedent for abandoning refs.

will see if we can get that fixed.

5 months ago

Metadata Update from @dustymabe:
- Issue status updated to: Open (was: Closed)

@puiterwijk helped us get this done. It is done now.

4 months ago

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Login to comment on this ticket.