mirror of
https://github.com/projectatomic/rpm-ostree.git
synced 2026-02-05 09:45:27 +01:00
28edfe620e
Closes: https://github.com/coreos/rpm-ostree/issues/3252 This avoids creating a magical, manual error prone step in the release process, at the cost of dealing with generated code in git.
1.2 KiB
1.2 KiB
parent, nav_order
| parent | nav_order |
|---|---|
| Contributing | 3 |
Releasing rpm-ostree
- Increment the
year_versionandrelease_versionmacros inconfigure.ac. - Increment the
Versionfield inrpm-ostree.spec.in. - Verify the libdnf deps in
rpm-ostree.spec.inare up to date by copy/pasting the relevant bits from the spec in the git submodule (libdnf/libdnf.spec). - Submit as a PR and wait until reviewed and CI is green.
- Once merged, do
git pull $upstream && git reset --hard $upstream/mainon your localmainbranch to make sure you're on the right commit. - Draft release notes by seeding a HackMD.io with
git shortlog $last_tag..and ideally collaborating with others. Filter out the commits fromdependabot. See previous releases for format. - Use
git-evtagto create a signed tag with the release notes as its content. Make the first line be the name of the tag itself. - Push the tag using
git push $upstream v202X.XX. - Create the xz tarball:
make -C packaging -f Makefile.dist-packaging dist-snapshot - Create a GitHub release for the new release tag using its contents and attach the tarball.