fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-20 07:00:05 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: update the process to release a VPN plugin

Browse source
This commit is contained in:
Íñigo Huguet 2025-08-25 13:34:54 +00:00
parent 94d7dd9b11
commit 79ffe55686
1 changed files with 17 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
MAINTAINERS.md
View file

@ -252,17 +252,25 @@ Versioning scheme (version numbers are called MAJOR.MINOR.MICRO):
versioning scheme than the main NM project despite there are no development versioning scheme than the main NM project despite there are no development
versions here. versions here.
Before starting:
- You need to have the maintainer role in the project.
- The GPG key used to sign the release must be added to your GNOME's Gitlab
profile and uploaded to a keyserver.
- All details: https://handbook.gnome.org/maintainers/making-a-release.html
When doing a release, follow this process: When doing a release, follow this process:
1. Ensure that `NEWS` file is up to date. 1. Ensure that `NEWS` file is up to date.
2. Increment the version in `meson.build`, commit and tag the commit. Example: 2. Increment the version in `meson.build` or `configure.ac`.
`git tag -s 1.2.8 -m 'Tag 1.2.8'`. 3. Commit and push to the `main` branch.
3. Ensure that you are on the right commit and create the tarball: 4. Check that the Gitlab's pipeline finishes without errors.
`git clean -fdx && meson setup build && cd build && meson dist` 5. Tag the commit with a signed tag. Example: `git tag -s 1.2.8 -m 'Release 1.2.8'`.
4. Upload the tarball: `scp ./*-*.tar.xz "$user@master.gnome.org:"` 6. Push the tag. Example: `git push origin 1.2.8`.
5. Login to `master.gnome.org` and run `ftpadmin install`. WARN: this is what starts the automatic CI release. As GNOME doesn't allow
Ensure the new tarballs show up at https://download.gnome.org/sources/ to delete tags, any error detected after this will force a new version bump.
(happens after a short delay) 7. Check that the Gitlab's pipeline finishes without errors. If that happens,
6. Announce the release on the mailing list. the release is done and available both in the Gitlab's releases section and
https://download.gnome.org/sources/*
8. Announce the release on the mailing list.
Notes: Notes:
- You need access to master.gnome.org, see [here](https://handbook.gnome.org/infrastructure/accounts.html). - You need access to master.gnome.org, see [here](https://handbook.gnome.org/infrastructure/accounts.html).