-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next: new release on 2020-10-07 (33.20201006.1.0) #197
Comments
If |
Please hold this release for now. We're really close to having the f33 bits all in, but it's not there just yet. |
We're getting much closer.. Pending a new version of coreos-installer and also we need to decide if we can wait til the next release to deal with coreos/fedora-coreos-tracker#646. |
|
|
Rollout is scheduled for tomorrow! |
First, verify that you meet all the prerequisites
Name this issue
next: new release on YYYY-MM-DD
with today's date. Once the pipeline spits out the new version ID, you can append it to the title e.g.(31.20191117.2.0)
.Pre-release
Promote next-devel changes to next
From the checkout for
fedora-coreos-config
(replaceupstream
below withwhichever remote name tracks
coreos/
):git fetch upstream
git checkout next
git reset --hard upstream/next
/path/to/fedora-coreos-releng-automation/scripts/promote-config.sh next-devel
git show
next
branch on https://github.com/coreos/fedora-coreos-configBuild
next
, leave all other defaults)Sanity-check the build
Using the the build browser for the
next
stream:next
release (in the future, we'll want to integrate this check in the release job)IMPORTANT: this is the point of no return here. Once the OSTree commit is
imported into the unified repo, any machine that manually runs
rpm-ostree upgrade
will have the new update.Run the release job
next
and the new version IDcosa run --qemu-image /path/to/previous.qcow2
) and verifying thatrpm-ostree upgrade
works andrpm-ostree status
shows a valid signature.At this point, Cincinnati will see the new release on its next refresh and create a corresponding node in the graph without edges pointing to it yet.
Refresh metadata (stream and updates)
From a checkout of this repo:
updates/next.json
:rollout
has astart_percentage
of1.0
) and set itsversion
to the most recent completed rolloutversion
field to the new versionstart_epoch
field to a future timestamp for the rollout start (e.g.date -d '20yy/mm/dd 14:30UTC' +%s
)start_percentage
field to0.0
duration_minutes
field to a reasonable rollout window (e.g.2880
for 48h)last-modified
field to current time (e.g.date -u +%Y-%m-%dT%H:%M:%SZ
)A reviewer can validate the
start_epoch
time by runningdate -u -d @<EPOCH>
. An example of encoding and decoding in one step:date -d '2019/09/10 14:30UTC' +%s | xargs -I{} date -u -d @{}
.sync-stream-metadata
job syncs the contents to S3Update graph manual check
NOTE: In the future, most of these steps will be automated.
Housekeeping
next-devel
stream to see if any overrides are obsolete. They are obsolete if the rpms have hit the stable fedora repos.The text was updated successfully, but these errors were encountered: