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
|
--- README-release.orig 2021-05-12 21:09:19.810266045 +0200
+++ README-release 2021-05-12 21:09:05.714122474 +0200
@@ -19,9 +19,9 @@
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/libidn2/-/pipelines
* Run the following command to download any new translations:
@@ -29,27 +29,26 @@
* 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'
+ make release-commit RELEASE='X.Y.Z TYPE'
* 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'
+ make release RELEASE='X.Y.Z 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-libidn2-X.Y.Z
that was just created by that "make" command.
Once all the builds and tests have passed,
@@ -57,7 +56,7 @@
* Run the gnupload command that was suggested by your "make release"
run above, or run
- make upload RELEASE='X.Y TYPE'
+ make upload RELEASE='X.Y.Z TYPE'
* Wait a few minutes (maybe up to 30?) and then use the release URLs to
download all tarball/signature pairs and use gpg --verify to ensure
@@ -68,28 +67,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 +75,4 @@
to update the on-line manual accessible at
- https://www.gnu.org/software/@PACKAGE@/manual/
+ https://www.gnu.org/software/libidn/libidn2/manual/
|
