keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
142d86dbeb
rpm-ostree/RELEASE.md
Jonathan Lebon fc1e660454 Move release instructions to RELEASE.md 
The instructions for doing a release were outdated. Take the opportunity
to just move it to a dedicated markdown file and breaking it out to make
it easier to follow.

This is one step short of using a release checklist like some of the
other CoreOS projects do. This is a good base to eventually do that if
we want.
2020-06-23 16:14:51 -04:00

998 B
Raw Blame History

Releasing rpm-ostree

  1. Increment the year_version and release_version macros in configure.ac.
  2. Increment the Version field in rpm-ostree.spec.in.
  3. Submit as a PR and wait until reviewed and CI is green.
  4. Once merged, do git pull $upstream && git reset --hard $upstream/master on your local master branch to make sure you're on the right commit.
  5. Draft release notes by seeding a HackMD.io with git shortlog $last_tag.. and ideally collaborating with others. Filter out the commits from dependabot. See previous releases for format.
  6. Use git-evtag to create a signed tag with the release notes as its content. Make the first line be the name of the tag itself.
  7. Push the tag using git push $upstream v202X.XX.
  8. Create the xz tarball using make -C packaging -f Makefile.dist-packaging dist-snapshot.
  9. Create a GitHub release for the new release tag using its contents and attach the tarball.