luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-03-13 19:25:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Update the release documentation for the new release workflow

Browse Source 
Make it more closely match
https://handbook.gnome.org/maintainers/making-a-release.html again.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>
This commit is contained in:
Philip Withnall 2025-01-23 13:59:48 +00:00
parent 884925d02e
commit d11dac3836
No known key found for this signature in database
GPG Key ID: C5C42CFB268637CA
1 changed files with 8 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/releasing.md
View File

@ -57,35 +57,27 @@ git add -p
git commit -sm "${new_version}" git commit -sm "${new_version}"
``` ```
Build the release tarball: Test build the release tarball:
```sh ```sh
ninja -C build/ dist meson dist -C build/
``` ```
Tag, sign and push the release (see below for information about `git evtag`): Tag, sign and push the release, using `${new_version}` as the tag message (see below for information about `git evtag`):
```sh ```sh
git evtag sign ${new_version} git evtag sign ${new_version}
git push --atomic origin ${branch} ${new_version} git push --atomic origin ${branch} ${new_version}
``` ```
To use a specific key add an option `-u ${keyid|email}` after the `sign` argument. You will need to **temporarily** allow maintainers to push to the `main` branch on https://gitlab.gnome.org/GNOME/glib/-/settings/repository. To use a specific key add an option `-u ${keyid|email}` after the `sign` argument.
Use `${new_version}` as the tag message. The `dist-job` CI job will be triggered and will build and upload the final release archive.
Upload the release tarball (you will need a
[GNOME LDAP account](https://wiki.gnome.org/Infrastructure/NewAccounts) for this):
```sh
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: Add the release notes to GitLab and close the milestone:
- Go to https://gitlab.gnome.org/GNOME/glib/-/tags/${new_version}/release/edit
and upload the release notes for the new release from the `NEWS` file
- Go to https://gitlab.gnome.org/GNOME/glib/-/releases/${new_version}/edit - Go to https://gitlab.gnome.org/GNOME/glib/-/releases/${new_version}/edit
and link the milestone to it, then list the new release tarball and and upload the release notes for the new release from the `NEWS` file
- Then link the milestone to it, then list the new release tarball and
`sha256sum` file in the ‘Release Assets’ section as the ‘Other’ types. `sha256sum` file in the ‘Release Assets’ section as the ‘Other’ types.
Get the file links from https://download.gnome.org/sources/glib/ and Get the file links from https://download.gnome.org/sources/glib/ and
name them ‘Release tarball’ and ‘Release tarball sha256sum’ name them ‘Release archive’ and ‘Release archive checksum’
- Go to https://gitlab.gnome.org/GNOME/glib/-/milestones/ - Go to https://gitlab.gnome.org/GNOME/glib/-/milestones/
choose the milestone and close it, as all issues and merge requests tagged choose the milestone and close it, as all issues and merge requests tagged
for this release should now be complete for this release should now be complete