templates: add checklist for rebasing to a new version of Fedora #806
Conversation
|
@dustymabe @jlebon PTAL and verify that I got the sequencing right. |
|
@bgilbert mostly LGTM. I've got some small things to add in a follow up. Should we just link to this template from the fedora-coreos-config README? It could get confusing if there is more than one place for things to live. |
|
@dustymabe I put the link in the fedora-coreos-config README (coreos/fedora-coreos-config#987) because I couldn't think of a better place to document it. I'm open to ideas. |
Oh man.. You did exactly what I was requesting.. I just didn't see you had already done it! Ignore me :) |
| ## Ship rebased `next` | ||
|
|
||
| - [ ] Ship `next` | ||
| - [ ] Set a new update barrier for N-2 on `next`. In the barrier entry set a link to [the docs](https://docs.fedoraproject.org/en-US/fedora-coreos/update-barrier-signing-keys/). See [discussion](https://github.com/coreos/fedora-coreos-tracker/issues/480#issuecomment-631724629). |
There was a problem hiding this comment.
Note this doesn't actually address the intended purpose: #749 (comment).
We'll need to revisit that eventually, but right now there's actually no use in adding these barriers.
There was a problem hiding this comment.
(or alternatively #810, mid-air collision 💥)
Based on the fedora-coreos-config README.