Repository navigation
Expand file tree
/
Copy pathRELEASE
More file actions
85 lines (54 loc) · 2.72 KB
/
Copy pathRELEASE
File metadata and controls
85 lines (54 loc) · 2.72 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
GCab Release Notes
This document describes the public release workflow. Local development may
use jj; the release commit, tag and push are done through git.
Note: if your working copy is a jj-colocated checkout, do not run git commit
or git tag against jj's detached HEAD. Use a normal git clone for the release,
or make sure the final release commit has already been exported to git.
--------------------------------------------------------------------------------
1. Prepare the release
- Update NEWS at your discretion before making the release commit.
- Update the project version in meson.build to the new release version.
- Make sure the release commit is the intended final commit and that the
working tree is clean:
git status --short
2. Build and test from a clean tree
meson setup _build .
meson compile -C _build
meson test -C _build --print-errorlogs
Optionally verify the release tarball builds and tests successfully:
meson dist -C _build
tar -xf _build/meson-dist/gcab-<version>.tar.xz -C /tmp
cd /tmp/gcab-<version>
meson setup _dist-build .
meson compile -C _dist-build
meson test -C _dist-build --print-errorlogs
3. Commit and push the release commit
Set the release version and tag:
export release_version="1.7"
export release_tag="${release_version}"
The version must match meson.build. The tag must be the bare version
number, without a "v" prefix, because GNOME's release service expects the
tarball to be named gcab-${release_tag}.tar.xz.
Stage only the intended release files (include NEWS if you updated it):
git add meson.build NEWS
git commit -m "Release ${release_version}"
git push origin HEAD
4. Create and push the signed tag
Follow the GNOME handbook. Preferred, if git-evtag is available:
git evtag sign "${release_tag}"
Fallback:
git tag -s -m "GCab ${release_version}" "${release_tag}"
Then push the tag:
git push origin "${release_tag}"
Do not use "git tag -f" for a final release tag. Do not prefix the tag with
"v": the release tarball must remain gcab-${release_tag}.tar.xz.
5. Release service (normal path)
The .gitlab-ci.yml pipeline includes the GNOME release-service. On a
protected release tag it:
- uses the tarball produced by the configured dist job ("build-gnomeos"),
- uploads the tarball and its sha256sum to download.gnome.org,
- creates the GitLab release from the tag message.
GNOME protects tags in the GNOME group automatically; ensure the tag was
accepted as protected, then monitor the pipeline until the release-service
job succeeds.
No manual upload is needed when the release service is available.