Skip to content
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

Release 0.15.0 #355

Closed
39 of 40 tasks
jlebon opened this issue Jun 6, 2022 · 3 comments
Closed
39 of 40 tasks

Release 0.15.0 #355

jlebon opened this issue Jun 6, 2022 · 3 comments
Assignees
Labels

Comments

@jlebon
Copy link
Member

jlebon commented Jun 6, 2022

Release checklist:

Tagging:

  • Write release notes in docs/release-notes.md. Get them reviewed and merged
    • If doing a branched release, also include a PR to merge the docs/release-notes.md changes into main
  • Ensure your local copy is up to date with the upstream main branch (git@github.com:coreos/butane.git)
  • Ensure your working directory is clean (git clean -fdx)
  • Ensure you can sign commits and any yubikeys/smartcards are plugged in
  • Run ./tag_release.sh <vX.Y.z> <git commit hash>
  • Push that tag to GitHub

Fedora packaging:

  • Update the Butane spec file in Fedora:
    • Bump the Version
    • Switch the Release back to 1%{?dist}
    • Remove any patches obsoleted by the new release
    • Run go-mods-to-bundled-provides.py | sort while inside of the butane directory you ran ./tag_release from & copy output into spec file in # Main package provides section
    • Update changelog
  • Run spectool -g -S butane.spec
  • Run kinit your_fas_account@FEDORAPROJECT.ORG
  • Run fedpkg new-sources tarball-name
  • PR the changes in Fedora
  • Once the PR merges to rawhide, merge rawhide into the other relevant branches (e.g. f35) then push those, for example:
    git checkout rawhide
    git pull --ff-only
    git checkout f35
    git merge --ff-only rawhide
    git push origin f35
  • On each of those branches run fedpkg build
  • Once the builds have finished, submit them to bodhi, filling in:
    • butane for Packages
    • Selecting the build(s) that just completed, except for the rawhide one (which gets submitted automatically)
    • Writing brief release notes like "New upstream release; see release notes at link to GitHub release"
    • Leave Update name blank
    • Type, Severity and Suggestion can be left as unspecified unless it is a security release. In that case select security with the appropriate severity.
    • Stable karma and Unstable karma can be set to 2 and -1, respectively.

GitHub release:

  • Wait until the Bodhi update shows "Signed ✔️" in the Metadata box.
  • File a releng ticket based on prior signing tickets.
    • Update the script and test it locally by running it like FAKESIGN=1 ./script
      • If a new Fedora release has gone stable, update the signing key in the script to use the new Fedora signing key found here.
  • Ping mboddu in Libera.Chat #fedora-coreos, linking to the ticket
  • Wait for the ticket to be closed
  • Download the artifacts and signatures
  • Verify the signatures
  • Find the new tag in the GitHub tag list and click the triple dots menu, and create a draft release for it.
  • Upload all the release artifacts and their signatures. Copy and paste the release notes from docs/release-notes.md here as well.
    • If the signing key has changed, note the change in the GitHub release notes as done here.
  • Publish the release

Quay release:

  • Visit the Quay tags page and wait for a versioned tag to appear
  • Click the gear next to the tag, select "Add New Tag", enter release, and confirm
  • Visit the Quay tags page for the legacy FCCT repo and wait for a versioned tag to appear
  • Click the gear next to the tag, select "Add New Tag", enter release, and confirm

RHCOS packaging for the current RHCOS development release:

  • Update the Butane spec file
    • Bump the Version
    • Switch the Release back to 1%{?dist}
    • Remove any patches obsoleted by the new release
    • Run go-mods-to-bundled-provides.py | sort while inside of the Butane directory you ran ./tag_release from & copy output into spec file in # Main package provides section
    • Update changelog
  • Run spectool -g -S butane.spec
  • Run kinit your_account@REDHAT.COM
  • Run rhpkg new-sources tarball-name
  • PR the changes
  • Get the PR reviewed and merge it
  • Update your local repo and run rhpkg build
  • File ticket similar to this one to sync the new version to mirror.openshift.com

Housekeeping:

@jlebon
Copy link
Member Author

jlebon commented Jun 6, 2022

@bgilbert
Copy link
Contributor

ART mirror ticket: https://issues.redhat.com/browse/ART-4165

@prestist
Copy link
Contributor

prestist commented Jun 28, 2022

releng ticket: https://pagure.io/releng/issue/10862

@bgilbert bgilbert closed this as completed Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants