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
126
127
128
129
130
131
132
133
134
|
README for MAKING BINUTILS RELEASES
This is a collection of notes on how to perform a binutils release. A
lot of this information can also be found in the maintain.texi file in
the gnulib project:
https://www.gnu.org/software/gnulib/
It is useful to have a cloned copy of the sources of this project as
it also contains an upload script used to install tarballs on the GNU
FTP server.
Make sure that you have upload authority on sourceware and fencepost.
Beware - this is an involved process and can take weeks to complete.
See the maintain.texi file for details on how to obtain these
permissions.
-------------------------------------------------
How to perform a release.
-------------------------------------------------
xxx -- fill in stuff here -- xxx
-------------------------------------------------
How to perform a point release.
-------------------------------------------------
A point release is easier than a normal release since a lot of the
work has already been done. The branch has been created, the
translations updated and the documentation uploaded. So the procedure
looks like this:
0. Decide that a point release is necessary.
Usually this only happens when a sufficient number of serious
bugs have been found and fixed since the previous release, and a
new official release is not imminent.
1. Tell the community that a point release is happening. Ask
maintainers to ensure that their ports are up to date on the
release branch. Ask the community if there are any bug fixes
which are missing from the branch. Allow some time for the
responses to this step.
2. Make sure that the branch sources build, test and install
correctly.
3. In the branch sources:
a. Update the minor release number in bfd/version.m4.
b. Edit bfd/development.sh and set "development=false".
c. Regenerate the configure files.
d. Commit the updates along with a "this-is-the-2.XX.X-release"
note in all of the changelogs.
e. Tag the branch with the new release number:
git tag -a binutils-2_XX_X
[optional: add "-u XXXXX" to sign with a gpg key]
git push origin binutils-2_XX_X
f. Check that your file creation mask will create the
correct file permissions. Eg:
umask 022
g. Create the release tarballs:
./src-release -b -g -l -x binutils
h. Check that the files in the tarballs have the correct
permissions.
i. Edit bfd/development.sh and set "development=true".
j. Commit this change into the git repository.
k. Clean up the source tree. (Use "git status" to find new
files, and remove them).
FIXME: The tarballs will contain spurious autom4te.cache
directories which could be removed to reduce their size.
4. [If paranoid - upload the tarballs to one of the FTP servers and
ask people to test it before going on to step 5].
5. Upload the tarballs to ftp.gnu.org.
gnupload --to ftp.gnu.org:binutils binutils-X.XX.X.tar.*
The gnupload script is in the gnulib/build-aux directory.
6. Upload the tarballs to sourceware.org:
sftp sourceware.org
cd /ftp/pub/binutils/releases
put binutils-X.XX.X.tar.*
chmod 644 binutils-X.XX.X.tar.*
quit
FIXME: Should the signatures (created by the gnupload script in
step 5) be uploaded as well ?
7. Update web pages. For sourceware.org:
* Log on to sourceware.org
* Go /www/htdocs/binutils
* Edit index.html
For the www.gnu.org site you have to email webmasters@gnu.org
and ask them to make the change(s).
8. Send an emails to the binutils list, info-gnu@gnu.org and
David Edelsohn <dje.gcc@gmail.com> announcing the new release.
(The email to Davis is so that he can update the GNU Toolchain
social media). Something like this:
------------------------------------------------------------------------
Hi Everyone,
We are pleased to announce that version 2.XX.X of the Binutils project
sources have been released and are now available for download at:
https://ftp.gnu.org/gnu/binutils
https://sourceware.org/pub/binutils/releases/
This is a point release over the previous 2.XX version, containing bug
fixes but no new features.
Our thanks go out to all of the binutils contributors, past and
present, for helping to make this release possible.
--------------------------------------------------------------------------
Copyright (C) 2017-2018 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.
|
