keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ba7a72995b
rpm-ostree/docs/RELEASE.md
Jonathan Lebon 8e22075721 RELEASE: Add step to update libdnf's deps 
In the latest release, we should've bumped librepo's requirement. It
doesn't use symbol versioning, so we don't automatically get this. At
release time at least, we should just peek at the spec we're baking in
and pick up from that.

Clearly the updated deps are in the buildroot if CI is green, so this
should mostly be a matter of bumping to versions which are already
shipped in Fedora.

See: https://github.com/rpm-software-management/libdnf/pull/1128
See: https://github.com/coreos/rpm-ostree/pull/2644
See: https://bugzilla.redhat.com/show_bug.cgi?id=1943773
2021-03-29 10:37:13 -04:00

1.1 KiB
Raw Blame History

nav_order
8

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. Verify the libdnf deps in rpm-ostree.spec.in are up to date by comparing to the spec of the bundled version (libdnf/libdnf.spec).
  4. Submit as a PR and wait until reviewed and CI is green.
  5. 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.
  6. 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.
  7. 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.
  8. Push the tag using git push $upstream v202X.XX.
  9. Create the xz tarball using make -C packaging -f Makefile.dist-packaging dist-snapshot.
  10. Create a GitHub release for the new release tag using its contents and attach the tarball.