luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-06 17:36:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
573b4e35d1
glib/docs/releasing.md
Philip Withnall 70cb59ec90 docs: Document the release process 
This documents what we already do, rather than trying to make any
improvements to the process. They can happen separately, later, as
they’re a little more involved than just writing a Markdown document.

For example, we really should automate some of this.

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2022-06-21 16:16:10 +01:00

4.0 KiB
Raw Blame History

Making a release

When to make a release

Releases are made on a schedule determined in the roadmap. Each release corresponds to a GitLab milestone.

There is usually some scope to change a release date by plus or minus a week, to allow specific merge requests to land if they are deemed as more important to release sooner rather than waiting until the next scheduled release. However, there is always another release, and releasing on time is more important than releasing with everything landed. Releasing on time allows distributors to schedule their packaging work efficiently.

Maintainers should take it in turns to make releases so that the load is spread out evenly and every maintainer is practiced in the process.

How to make a release

Broadly, GLib follows the same process as every other GNOME module.

These instructions use the following variables:

  • new_version: the version number of the release you are making, for example 2.73.1
  • previous_version: the version number of the most-recently released version in the same release series, for example 2.73.0
  • branch: the branch which the release is based on, for example glib-2-72 or main

Make sure your repository is up to date and doesn’t contain local changes:

git pull
git status

Check the version in meson.build is correct for this release.

Download gitlab-changelog and use it to write a NEWS entry:

gitlab-changelog.py GNOME/glib ${previous_version}..

Copy this into NEWS, and manually write some highlights of the fixed bugs as bullet points at the top. Most changes won’t need to be highlighted — only the ones which add APIs, change dependencies or packaging requirements, or fix impactful bugs which might affect distros’ decisions of how to prioritise the GLib release or how urgent to mark it as.

You can get review of your NEWS changes from other co-maintainers if you wish.

Commit the release:

git add -p
git commit -sm "${new_version}"

Build the release tarball:

ninja -C build/ dist

Tag, sign and push the release (see below for information about git evtag):

git evtag sign ${new_version}
git push --atomic origin ${branch} ${new_version}

To use a specific key add an option -u ${keyid|email} after the sign argument.

Use ${new_version} as the tag message.

Upload the release tarball (you will need a GNOME LDAP account for this):

scp build/meson-dist/glib-${new_version}.tar.xz master.gnome.org:
ssh master.gnome.org ftpadmin install glib-${new_version}.tar.xz

Add the release notes to GitLab and close the milestone:

git-evtag

Releases must be done with git evtag rather than git tag, as it provides stronger security guarantees. See its documentation for more details. In particular, it calculates its checksum over all blobs reachable from the tag, including submodules; and uses a stronger checksum than SHA-1.

You will need a GPG key for this, ideally which has been signed by others so that it can be verified as being yours. However, even if your GPG key is unsigned, using git evtag is still beneficial over using git tag.