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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
|
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.
-------------------------------------------------
1. Send an email out warning contributors about the forthcoming
branch. Set a date for the branch (weekends are better because
they are less busy).
2. When the branch date is near: Update the libiberty and config
directories and the top level configure files.
3. When branch day arrives add markers for the upcoming release to
gas, ld, gold and binutils NEWS files.
[If using the make-prerelease.sh script, check that
common.sh has the right values].
[make-prelease.sh command i]
Likewise for all of the ChangeLog files.
Add a note of the name of the new branch to binutils/BRANCHES.
Commit these changes.
[make-prerelease.sh command C]
4. Create the release branch using:
git branch binutils-2_31-branch
git push origin binutils-2_31-branch
5. Make sure that the branch is there. IE check out the branch sources:
git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_31-branch 2.31
If you get a message about being in a "detached head" state, something
has gone wrong...
6. Update "BINUTILS_BRANCH" in gdbadmin's crontab:
Log in as gdbadmin on sourceware.org, and then:
$ cd crontab
$ vi crontab
[change BINUTILS_BRANCH]
$ cvs ci crontab
$ crontab crontab
If you do not have access to this account, please feel free to
ask Joel Brobecker <brobecker AT adacore DOT com>.
7. Rename the current HEAD version entry in Bugzilla, and create a
new one. E.g. rename "2.30 (HEAD)" to 2.30, and create "2.31
(HEAD)":
https://sourceware.org/bugzilla/editversions.cgi?product=binutils
8. Update bfd/version.m4 on HEAD to indicate that is now a snapshot
of the next release:
m4_define([BFD_VERSION], [2.31.51])
Update the release number in bfd/version.m4 for the branch.
The branch only needs the point value set to 90 as the release
has not actually happened yet.
m4_define([BFD_VERSION], [2.30.90])
Regenerate various files on both branch and HEAD by configuring
with --enable-maintainer-mode. NB/ Remember to build gold and
gprof. Add ChangeLog entries. Commit the changes. Make sure
that this includes the .pot files as well as the configure and
makefiles.
8. Create an initial prerelease:
a. Create a source tarball of the BRANCH sources:
./src-release -x binutils
b. Build a test target using this tarball.
c. Upload the prerelease snapshot to the FTP:
scp ../binutils-$version.tar.xz sourceware.org:~ftp/pub/binutils/snapshots
ssh sourceware.org md5sum ~ftp/pub/binutils/snapshots/binutils-$version.tar.xz
d. Clean up the source directory.
9. Tell the Translation Project where to find the new tarball. <coordinator@translationproject.org>
qv: http://translationproject.org/html/maintainers.html
------------------------------------------------------------------------
Dear Translation Project
The 2.31 release branch has been created for the FSF binutils.
A snapshot of the branch sources can be found here:
https://sourceware.org/pub/binutils/snapshots/binutils-2.30.90.tar.xz
We hope to make the official release of the sources on the 8th July
although that could change if there are important bugs that need to
be fixed before the release.
------------------------------------------------------------------------
10. Announce the availability of the snapshot and the branch on the
binutils mailing list. Set a date for when the release will
actually happen. Something like:
------------------------------------------------------------------------
Hi Everyone,
The 2.XX branch has now been created:
git clone git://sourceware.org/git/binutils-gdb.git -b binutils-2_XX-branch 2.XX
A snapshot of the sources is also available here:
https://sourceware.org/pub/binutils/snapshots/binutils-2.XX.90.tar.xz
Please could all patches for the branch be run by me.
The rules for the branch are:
* No new features.
* Target specific bug fixes are OK.
* Generic bug fixes are OK if they are important and widely tested.
* Documentation updates/fixes are OK.
* Translation updates are OK.
* Fixes for testsuite failures are OK.
Ideally I would like to make the release happen in two weeks time,
i.e. Saturday 27th Jan. Which I hope will be enough time for everyone
to get their final fixes in.
------------------------------------------------------------------------
11. Build various different toolchains, test them and nag
maintainers to fix any testsuite failures for their
architectures...
When the time comes to actually make the release....
20. Make sure that the branch sources still build, test and install
correctly. Make sure that the sources are clean, without any
patch files (.reg .orig *~) left over.
cd <branch>
cvsclean | xargs rm
21. Update the release number in bfd/version.m4 on the release
branch to a whole new minor version number, without a point
value. Eg "2.29.90" becomes "2.30". Change bfd/development.sh
to set all values to "false". Regenerate the configure and
makefiles. And *info* files. Add ChangeLog entries for the
updates and add a "this-is-the-2.XX-release" comment and
commit. Make sure to include the .gmo files.
22. Check that your file creation mask will create the
correct file permissions. Eg:
% umask
22
Remove any spurious autom4te.cache files left over from the
reconfiguring:
% find . -depth -name autom4te.cache -exec rm -r {} \;
23. Note - check to see if any new files have been added to the top
level of the source directory, but which are not in the
DEVO_SUPPORT variable in the src-release.sh script. If they are
needed then add them.
Create the release tarballs:
./src-release.sh -b -g -l -x binutils
24. Check that the files in the tarballs have the correct
permissions.
25. Sanity check the release on x86_64-pc-linux-gnu by building and
running the testsuite. Make the source directory read-only
before building. Also test "make install". If necessary fix
any problems.
26. Tag the branch with the new release number:
git tag -a binutils-2_XX
[optional: add "-u XXXXX" to sign with a gpg key]
git push origin binutils-2_XX
NB/ If you do sign the binaries make sure to use a key
that has been published with the FSF.
27. Upload the tarballs to ftp.gnu.org.
gnupload --to ftp.gnu.org:binutils binutils-X.XX.tar.*
The gnupload script is in the gnulib/build-aux directory.
Check for an email response from the upload. If necessary
fix any problems.
28. Upload the tarballs (and signatures) to sourceware.org:
sftp sourceware.org
cd /sourceware/ftp/pub/binutils/releases
put binutils-X.XX.tar.*
chmod 644 binutils-X.XX.tar.*
quit
FIXME: Should the signatures (created by the gnupload script in
step 29) be uploaded as well ?
29. Update web pages. For sourceware.org:
Create a new documentation folder on the sourceware.org web
pages as /sourceware/www/sourceware/htdocs/binutils/docs-X.XX.
Make the html documentation locally with the "make html" command
and then upload and rename the directories as needed. (sftp
does not appear to support recursive uploads however, so the
directories will have to be made by hand). Create an
index.html file and then edit the docs link to point to the new
docs-X.XX directory.
Update the index.html file in the directory containing the
docs-X.XX entries to point to the new documentation and mention
the new version.
For the www.gnu.org site you have to email webmasters@gnu.org
and ask them to make the change(s).
30. Send emails to binutils@sourceware.org, info-gnu@gnu.org and
David Edelsohn <dje.gcc@gmail.com> announcing the new release.
Sign the email and include the checksum.
(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 of the GNU 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/
checksums: xxxx
This release contains numerous bug fixes, and also the
following new features:
<extract info from the NEWS files>
Our thanks go out to all of the binutils contributors, past and
present, for helping to make this release possible.
--------------------------------------------------------------------------
31. Clean up the source tree. (Use "git status" to find new
files, and remove them).
32. Edit bfd/development.sh on the branch and set
"development=true". Also bump the version in bfd/version.m4 by
adding a trailing .0, so that the date suffix keeps the version
lower than the trunk version. Regenerate files. Commit these
changes.
33. Email the binutils list telling everyone that the 2.31 branch
is now open for business as usual and that patched no longer
need special approval.
-------------------------------------------------
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.
2.5 Prepare a list of the bugs which have been fixed. This
will be needed for step 8.
3. In the branch sources:
a. Update the minor release number in bfd/version.m4.
b. Edit bfd/development.sh, set "development=false" and
"experimental=false".
c. Regenerate the configure files.
c.1. Remove spurious autom4te.cache files:
find . -depth -name autom4te.cache -exec rm -r {} \;
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).
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 /sourceware/ftp/pub/binutils/releases
put binutils-X.XX.X.tar.*
chmod 644 binutils-X.XX.X.tar.*
quit
It is OK to upload the signatures as well.
7. Update web pages. For sourceware.org:
* Log on to sourceware.org
* Go to /sourceware/www/sourceware/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 GNU 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.
Here is a list of the bugs that have been fixed:
xx
xx
xx
xx
--------------------------------------------------------------------------
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.
|
