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
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
--- ../gnulib/top/README-release 2024-01-01 10:31:35.716121115 +0100
+++ README-release 2024-12-29 03:26:17.653478304 +0100
@@ -2,13 +2,25 @@
* Start from a clean, up-to-date git directory on "master":
- make -k maintainer-clean || { ./configure && make maintainer-clean; }
git checkout master
git pull origin master
+ git clean -d -x -f
+ git reset --hard
* Ensure that the latest stable versions of autoconf, automake, etc.
- are in your PATH. See the buildreq list in bootstrap.conf for
- the complete list of tools.
+ are in your PATH. See the buildreq list in bootstrap.conf for the
+ complete list of tools.
+
+* Ensure that all significant changes since the last release (use
+ "make review-diff") are reflected in NEWS.
+
+* Ensure that you have incremented the LT_* variables in configure.ac
+ properly. The sc_libtool_version_bump "make syntax-check" rule
+ should catch this.
+
+* Ensure that you have updated STRINGPREP_VERSION in lib/stringprep.h
+ for the current release. The tests/tst_version self-check should
+ catch this.
* Ensure that you have no uncommitted diffs. This should produce no
output:
@@ -19,39 +31,50 @@
git push origin master
-* Check that the NixOS/Hydra autobuilder is reporting all is well:
+* Check that the GitLab autobuilder is reporting all is well:
- https://hydra.nixos.org/project/gnu/@PACKAGE@-master
+ https://gitlab.com/libidn/libidn/-/pipelines
* Run the following command to download any new translations:
- ./bootstrap && ./configure
+ ./bootstrap
+ ./configure --enable-java --enable-gtk-doc-pdf
* Pre-release testing: ensure that the following commands succeed:
- c=check ve=check-very-expensive; git grep -q "^$ve:\$" && c=$ve
- make $c syntax-check distcheck
+ make check syntax-check distcheck
* To (i) set the date, version number, and release TYPE on line 3 of
NEWS, (ii) commit that, and (iii) tag the release, run
# "TYPE" must be stable, beta or alpha
- make release-commit RELEASE='X.Y TYPE'
+ env TZ=UTC0 make release-commit RELEASE='X.Y TYPE'
+
+* Push the tag to allow the GitLab pipeline to build reproducible
+ source tarballs.
+
+ git push origin tag $(git describe)
+
+ Don't delay over midnight UTC0 to perform the next step, because
+ otherwise the maint.mk "news-check" rule will fail.
* Run the following to create release tarballs. Your choice selects the
corresponding upload-to destination in the emitted gnupload command.
The different destinations are specified in cfg.mk. See the definitions
of gnu_ftp_host-{alpha,beta,stable}.
- make release RELEASE='X.Y TYPE'
+ env TZ=UTC0 make release RELEASE='X.Y TYPE'
* Test the tarball. Copy it to a few odd-ball systems and ensure that
it builds and passes all tests.
* While that's happening, write the release announcement that you will
- soon post. Start with the template, $HOME/announce-@PACKAGE@-X.Y
+ soon post. Start with the template, $HOME/announce-libidn-X.Y
that was just created by that "make" command.
+* Increment STRINGPREP_VERSION in lib/stringprep.h and LT_REVISION in
+ configure.ac for the next release.
+
Once all the builds and tests have passed,
* Run the gnupload command that was suggested by your "make release"
@@ -68,28 +91,6 @@
v=$(cat .prev-version)
git push origin master tag v$v
-* Announce it on Savannah first, so you can include the savannah.org
- announcement link in the email message.
-
- Go to the news-submission form:
-
- https://savannah.gnu.org/news/submit.php?group=@PACKAGE@
-
- If it does not work, then enable "News" for the project via this link:
-
- https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@
-
- Write something like the following:
-
- Subject: @PACKAGE@-X.Y released [stable]
- +verbatim+
- ...paste the announcement here...
- -verbatim-
-
- Then go here to approve it:
-
- https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
-
* Send the announcement email message.
* After each non-alpha release, run
@@ -98,4 +99,4 @@
to update the on-line manual accessible at
- https://www.gnu.org/software/@PACKAGE@/manual/
+ https://www.gnu.org/software/libidn/manual/
|
