]>
Commit | Line | Data |
---|---|---|
78b2179a | 1 | README for MAKING BINUTILS RELEASES |
a960d29f | 2 | |
78b2179a NC |
3 | This is a collection of notes on how to perform a binutils release. A |
4 | lot of this information can also be found in the maintain.texi file in | |
5 | the gnulib project: | |
6 | ||
7 | https://www.gnu.org/software/gnulib/ | |
8 | ||
9 | It is useful to have a cloned copy of the sources of this project as | |
10 | it also contains an upload script used to install tarballs on the GNU | |
11 | FTP server. | |
12 | ||
13 | Make sure that you have upload authority on sourceware and fencepost. | |
14 | Beware - this is an involved process and can take weeks to complete. | |
15 | See the maintain.texi file for details on how to obtain these | |
16 | permissions. | |
17 | ||
18 | ------------------------------------------------- | |
19 | How to perform a release. | |
20 | ------------------------------------------------- | |
21 | ||
98ab9e96 NC |
22 | 1. Send an email out warning contributors about the forthcoming |
23 | branch. Set a date for the branch (weekends are better because | |
24 | they are less busy). | |
a960d29f | 25 | |
7ab82037 | 26 | 2. When the branch date is near: Update the libiberty and config |
055bc77a NC |
27 | directories and the top level Makefile and configure files. Also |
28 | consider updating the toplevel libtool files. | |
98ab9e96 | 29 | |
be2c7885 NC |
30 | |
31 | Approx time to complete from here: 2 hours .... | |
32 | ||
826eed80 NC |
33 | 2.5 If you have not built from the sources recently then now is the |
34 | time to check that they still work... | |
a72b0718 | 35 | |
98ab9e96 | 36 | 3. When branch day arrives add markers for the upcoming release to |
03d0d46a NC |
37 | the NEWS files in gas, ld, and binutils. No need to update NEWS |
38 | in the gold directory - it has its own release numbering. | |
f974f26c NC |
39 | |
40 | Likewise for the ChangeLog files in: bfd, binutils, config, cpu, | |
a72b0718 | 41 | elfcpp, gas, gold, gprof, include, ld, libctf, opcodes and toplevel. |
f974f26c | 42 | |
9176ac5b | 43 | Add a note of the name of the new branch to binutils/BRANCHES. |
f974f26c | 44 | |
9176ac5b | 45 | Commit these changes. |
a960d29f | 46 | |
98ab9e96 NC |
47 | 4. Create the release branch using: |
48 | ||
631ec08c NC |
49 | git branch binutils-2_40-branch |
50 | git push origin binutils-2_40-branch | |
f48dfe41 NC |
51 | |
52 | If you get a message like: | |
53 | ||
54 | remote: fatal: Invalid revision range 0000000000000000000000000000000000000000..f974f26cb16cc6fe3946f163c787a05e713fb77b | |
55 | ||
56 | It appears that this can be ignored... | |
98ab9e96 | 57 | |
79d89b55 NC |
58 | 5. Make sure that the branch is there. IE check out the branch sources: |
59 | ||
631ec08c | 60 | git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_40-branch 2.40 |
79d89b55 NC |
61 | |
62 | If you get a message about being in a "detached head" state, something | |
63 | has gone wrong... | |
64 | ||
082cbd3b NC |
65 | Keep the checked out sources - they are going to be needed in future |
66 | steps. | |
f48dfe41 | 67 | |
79d89b55 | 68 | 6. Update "BINUTILS_BRANCH" in gdbadmin's crontab: |
0dd86f32 JB |
69 | |
70 | Log in as gdbadmin on sourceware.org, and then: | |
71 | ||
72 | $ cd crontab | |
73 | $ vi crontab | |
74 | [change BINUTILS_BRANCH] | |
75 | $ cvs ci crontab | |
76 | $ crontab crontab | |
77 | ||
78 | If you do not have access to this account, please feel free to | |
79 | ask Joel Brobecker <brobecker AT adacore DOT com>. | |
80 | ||
79d89b55 | 81 | 7. Rename the current HEAD version entry in Bugzilla, and create a |
346d80ef NC |
82 | new one. E.g. rename "2.38 (HEAD)" to 2.38, and create |
83 | "2.39 (HEAD)": | |
7ab82037 NC |
84 | |
85 | https://sourceware.org/bugzilla/editversions.cgi?product=binutils | |
98ab9e96 | 86 | |
71300e2c | 87 | 8. Update bfd/version.m4 on HEAD to indicate that is now a snapshot |
631ec08c NC |
88 | of the next release and the BRANCH to indicated that it is almost |
89 | ready for the release. | |
90 | ||
91 | So if the release is going to be 2.40 then the version number on | |
92 | the BRANCH should be set to 2.39.90 - ie almost, but not quite 2.40, | |
93 | and the version number on the MAINLINE should be set to 2.40.50 - | |
94 | ie half way to 2.41 release. | |
5f7a57f1 NC |
95 | |
96 | So the branch bfd/version.m4 has: | |
71300e2c | 97 | |
631ec08c | 98 | m4_define([BFD_VERSION], [2.39.90]) |
71300e2c | 99 | |
5f7a57f1 | 100 | and the mainline has: |
71300e2c | 101 | |
631ec08c | 102 | m4_define([BFD_VERSION], [2.40.50]) |
94c2436b NC |
103 | |
104 | Regenerate various files on both branch and HEAD by configuring | |
bb368aad VM |
105 | with "--enable-maintainer-mode --enable-gold --enable-shared" and then building |
106 | with "make all-binutils all-gas all-gold all-gprof all-gprofng all-ld" | |
f48dfe41 NC |
107 | |
108 | Add ChangeLog entries for the updated files. Commit the changes. | |
109 | Make sure that this includes the .pot files as well as the | |
110 | configure and makefiles. | |
98ab9e96 | 111 | |
b248e9ce | 112 | 9. Create an initial pre-release: |
98ab9e96 | 113 | |
04d7fa21 NC |
114 | a. Remove any auto-generated files, in order to force the |
115 | src-release script to rebuild them. | |
116 | ||
117 | cd <branch-sources> | |
be2c7885 | 118 | git clean -fdx |
04d7fa21 NC |
119 | |
120 | b. Create a source tarball of the BRANCH sources: | |
a960d29f | 121 | |
bb368aad | 122 | ./src-release.sh -x binutils |
a960d29f | 123 | |
04d7fa21 | 124 | c. Build a test target using this tarball. |
98ab9e96 | 125 | |
e1ec7b9f | 126 | cp binutils-2.39.90.tar.xz /dev/shm |
be2c7885 | 127 | pushd /dev/shm |
e1ec7b9f | 128 | tar xvf binutils-2.39.90.tar.xz |
375cd423 NC |
129 | mkdir build |
130 | cd build | |
e1ec7b9f | 131 | ../binutils-2.39.90/configure --quiet --enable-gold |
375cd423 | 132 | make |
be2c7885 | 133 | popd |
98ab9e96 | 134 | |
375cd423 NC |
135 | If there are problems, fix them. |
136 | ||
04d7fa21 | 137 | d. Upload the pre-release snapshot to the sourceware FTP site: |
375cd423 | 138 | |
e1ec7b9f NC |
139 | scp binutils-2.39.90.tar.xz sourceware.org:/var/ftp/pub/binutils/snapshots |
140 | ssh sourceware.org sha256sum ~ftp/pub/binutils/snapshots/binutils-2.39.90.tar.xz | |
98ab9e96 | 141 | |
04d7fa21 NC |
142 | e. Clean up the source directory again. |
143 | ||
be2c7885 | 144 | git clean -fdx |
375cd423 | 145 | |
b248e9ce | 146 | 10. Tell the Translation Project where to find the new tarball. |
082cbd3b | 147 | <coordinator@translationproject.org> |
be2c7885 | 148 | qv: https://translationproject.org/html/maintainers.html |
79d89b55 NC |
149 | |
150 | ------------------------------------------------------------------------ | |
151 | Dear Translation Project | |
152 | ||
e1ec7b9f | 153 | The 2.40 release branch has been created for the GNU Binutils project. |
79d89b55 NC |
154 | |
155 | A snapshot of the branch sources can be found here: | |
a960d29f | 156 | |
e1ec7b9f | 157 | https://sourceware.org/pub/binutils/snapshots/binutils-2.39.90.tar.xz |
a960d29f | 158 | |
b248e9ce | 159 | We hope to make the official release of the sources on the <DATE> |
79d89b55 NC |
160 | although that could change if there are important bugs that need to |
161 | be fixed before the release. | |
162 | ------------------------------------------------------------------------ | |
98ab9e96 | 163 | |
b248e9ce | 164 | 11. Announce the availability of the snapshot and the branch on the |
98ab9e96 | 165 | binutils mailing list. Set a date for when the release will |
7ab82037 | 166 | actually happen. Something like: |
79d89b55 NC |
167 | |
168 | ------------------------------------------------------------------------ | |
169 | Hi Everyone, | |
170 | ||
b248e9ce | 171 | The <NEW_VERSION> branch has now been created: |
79d89b55 | 172 | |
4b51505e | 173 | git clone git://sourceware.org/git/binutils-gdb.git -b binutils-<NEW_VERSION>-branch |
79d89b55 NC |
174 | |
175 | A snapshot of the sources is also available here: | |
176 | ||
b248e9ce | 177 | https://sourceware.org/pub/binutils/snapshots/binutils-<OLD_VERSION>.90.tar.xz |
79d89b55 NC |
178 | |
179 | Please could all patches for the branch be run by me. | |
180 | The rules for the branch are: | |
181 | ||
182 | * No new features. | |
183 | * Target specific bug fixes are OK. | |
184 | * Generic bug fixes are OK if they are important and widely tested. | |
185 | * Documentation updates/fixes are OK. | |
186 | * Translation updates are OK. | |
187 | * Fixes for testsuite failures are OK. | |
188 | ||
189 | Ideally I would like to make the release happen in two weeks time, | |
b248e9ce | 190 | i.e. <DATE>. Which I hope will be enough time for everyone |
79d89b55 NC |
191 | to get their final fixes in. |
192 | ------------------------------------------------------------------------ | |
193 | ||
b248e9ce | 194 | 12. Build various different toolchains, test them and nag |
7ab82037 NC |
195 | maintainers to fix any testsuite failures for their |
196 | architectures... | |
197 | ||
b248e9ce | 198 | ============================================================================== |
98ab9e96 | 199 | |
94c2436b NC |
200 | When the time comes to actually make the release.... |
201 | ||
202 | ||
9a5db26e | 203 | 20. Make sure that the branch sources still build, test and install |
6cb624f8 NC |
204 | correctly. Make sure that the sources are clean, without any |
205 | patch files (.reg .orig *~) left over. | |
206 | ||
207 | cd <branch> | |
9b351c9b | 208 | git clean -fdx |
9a5db26e | 209 | |
0f38fd87 NC |
210 | 21. a. Update the release number in bfd/version.m4 on the release |
211 | branch to a whole new minor version number, without a point | |
5ee285ca NC |
212 | value. Eg "2.39.90" becomes "2.40". |
213 | ||
0f38fd87 | 214 | b. Change bfd/development.sh to set all values to "false". |
5ee285ca | 215 | |
0f38fd87 NC |
216 | c. Regenerate the configure and makefiles. And *info* files. |
217 | ||
5ee285ca NC |
218 | make all-gas all-ld all-binutils all-gprof all-gold all-gprofng |
219 | make info | |
220 | ||
0f38fd87 NC |
221 | d. Create a ChangeLog from the git refs for all of the commits |
222 | from when changelog entries were no longer required: | |
223 | ||
224 | gitlog-to-changelog --since=2021-07-03 > ChangeLog.git | |
5ee285ca | 225 | git add ChangeLog.git |
0f38fd87 | 226 | |
5ee285ca NC |
227 | The gitlog-to-changelog script is part of the sources |
228 | of the "config" project. | |
0f38fd87 | 229 | |
5ee285ca NC |
230 | e. Add ChangeLog entries for all of the updates and add a |
231 | "this-is-the-2.38-release" comment and commit. | |
9a5db26e | 232 | |
5ee285ca NC |
233 | git commit |
234 | git push | |
235 | ||
9a5db26e NC |
236 | 22. Check that your file creation mask will create the |
237 | correct file permissions. Eg: | |
238 | ||
6cb624f8 NC |
239 | % umask |
240 | 22 | |
241 | ||
242 | Remove any spurious autom4te.cache files left over from the | |
243 | reconfiguring: | |
244 | ||
cb6ad9bb | 245 | git clean -fdx |
9a5db26e | 246 | |
ad96220c NC |
247 | 23. Note - check to see if any new files have been added to the top |
248 | level of the source directory, but which are not in the | |
249 | DEVO_SUPPORT variable in the src-release.sh script. If they are | |
5ee285ca | 250 | needed then add them. |
ad96220c | 251 | |
0f38fd87 | 252 | Create the release tarballs: |
9a5db26e | 253 | |
6cb624f8 | 254 | ./src-release.sh -b -g -l -x binutils |
9a5db26e | 255 | |
f54c53e9 NC |
256 | OR ... for a more reproducible tarball: |
257 | ||
258 | ./src-release.sh -b -g -l -x -r `git log -1 --format=%cd --date=format:%F bfd/version.m4` binutils | |
259 | ||
9a5db26e | 260 | 24. Check that the files in the tarballs have the correct |
07233d96 NC |
261 | permissions. |
262 | ||
5ee285ca | 263 | tar tvf binutils-*.tar.bz2 | grep -e "---" |
9a5db26e | 264 | |
88ae41e1 NC |
265 | Also check that the man files are not empty. (cf PR 28144). |
266 | ||
5ee285ca | 267 | tar tvf binutils-*.tar.xz | grep -e "\.1" |
88ae41e1 | 268 | |
9a5db26e | 269 | 25. Sanity check the release on x86_64-pc-linux-gnu by building and |
082cbd3b | 270 | running the testsuites (gas, gold, binutils and ld). Make the |
5ee285ca NC |
271 | source directory read-only before building. (Note - the gprofng |
272 | sources need a writeable doc/ directory. This is a bug that needs | |
273 | to be fixed). | |
274 | Also test "make install". | |
275 | If necessary fix any problems. | |
9a5db26e | 276 | |
0f38fd87 | 277 | pushd /dev/shm |
cb6ad9bb NC |
278 | mkdir delme |
279 | cd delme | |
07233d96 | 280 | tar xvf <path-to-sources>/binutils-2.*.tar.lz |
9b351c9b | 281 | chmod -R -w binutils-2.* |
5ee285ca | 282 | chmod +w binutils-2.*/gprofng/doc |
cb6ad9bb NC |
283 | mkdir build |
284 | cd build | |
bb368aad VM |
285 | ../binutils-2.*/configure --quiet --enable-gold --prefix=`pwd`/install --enable-plugins --enable-shared |
286 | make all-gas all-gold all-ld all-binutils all-gprof all-gprofng | |
cb6ad9bb | 287 | make check-gas check-binutils check-ld check-gold |
5ee285ca | 288 | make install-gas install-gold install-ld install-binutils install-gprofng |
cb6ad9bb | 289 | |
bf772a1e | 290 | # Needed for step 29... |
354c317e | 291 | make html pdf |
bf772a1e | 292 | |
0f38fd87 | 293 | popd |
5ee285ca | 294 | |
9a5db26e | 295 | 26. Tag the branch with the new release number: |
0f38fd87 NC |
296 | [optional: add "-u XXXXX" to sign with a gpg key] |
297 | enter a tag message such as: "Official GNU Binutils 2.3x release" | |
9a5db26e | 298 | |
5ee285ca | 299 | git tag -a binutils-2_40 -u DD9E3C4F <=== Be careful to get the tag right |
07233d96 | 300 | |
a8d6d6ac NC |
301 | NB/ If you do sign the binaries make sure to use a key |
302 | that has been published with the FSF. | |
303 | ||
cb6ad9bb NC |
304 | Then push the release: |
305 | ||
5ee285ca | 306 | git push origin binutils-2_40 |
cb6ad9bb | 307 | |
0f38fd87 NC |
308 | If you get an error message along the lines of: |
309 | "Invalid revision range ..." you can ignore it. | |
cb6ad9bb | 310 | |
0f38fd87 | 311 | 27. Upload the tarballs to ftp.gnu.org. |
9a5db26e | 312 | |
0f38fd87 | 313 | gnupload --to ftp.gnu.org:binutils binutils-2.3*.tar.* |
9a5db26e | 314 | |
0f38fd87 NC |
315 | Be prepared to provide the password for the key, if you |
316 | signed the binaries. | |
9b351c9b | 317 | |
0f38fd87 | 318 | The gnupload script is in the gnulib/build-aux directory. |
9a5db26e | 319 | |
0f38fd87 NC |
320 | Check for an email response from the upload. If necessary |
321 | fix any problems. | |
a8d6d6ac | 322 | |
6cb624f8 | 323 | 28. Upload the tarballs (and signatures) to sourceware.org: |
9a5db26e NC |
324 | |
325 | sftp sourceware.org | |
326 | cd /sourceware/ftp/pub/binutils/releases | |
9b351c9b | 327 | put binutils-2.3*.tar.* |
5ee285ca | 328 | chmod 644 binutils-2.3*.tar.* |
9a5db26e NC |
329 | quit |
330 | ||
0f38fd87 NC |
331 | FIXME: Are the signatures (created by the gnupload script in step 27) |
332 | needed ? [The above commands upload them and nobody has complained, | |
333 | so suggest that they are retained]. | |
9a5db26e | 334 | |
6cb624f8 | 335 | 29. Update web pages. For sourceware.org: |
9a5db26e NC |
336 | |
337 | Create a new documentation folder on the sourceware.org web | |
04d7fa21 | 338 | pages as /sourceware/www/sourceware/htdocs/binutils/docs-2.3x. |
082cbd3b NC |
339 | |
340 | sftp sourceware.org | |
341 | cd /sourceware/www/sourceware/htdocs/binutils | |
04d7fa21 NC |
342 | mkdir docs-2.3x |
343 | cd docs-2.3x | |
07233d96 NC |
344 | mkdir as |
345 | mkdir bfd | |
346 | mkdir binutils | |
347 | mkdir gprof | |
348 | mkdir ld | |
04d7fa21 | 349 | cd ../docs-2.3(x-1) |
082cbd3b NC |
350 | get index.html |
351 | ||
352 | Update the (local copy of the) index.html file to point to the | |
353 | new documentation and mention the new version and then upload it. | |
354 | ||
04d7fa21 | 355 | cd ../docs-2.3x |
082cbd3b NC |
356 | put index.html |
357 | ||
9a5db26e | 358 | Make the html documentation locally with the "make html" command |
9b351c9b NC |
359 | (see step 25 above). Then upload and rename the directories as |
360 | needed. (sftp does not appear to support recursive uploads | |
361 | however, so the directories had to be made by hand, as shown above). | |
082cbd3b NC |
362 | |
363 | cd as | |
07233d96 NC |
364 | lcd <build-dir>/gas/doc/as |
365 | put * {be patient - this takes a long time...} | |
366 | lcd .. | |
367 | cd .. | |
354c317e MF |
368 | put as.html |
369 | put as.pdf | |
1da0b075 | 370 | |
0f38fd87 | 371 | cd bfd |
07233d96 NC |
372 | lcd ../../bfd/doc/bfd |
373 | put * | |
374 | cd .. | |
375 | lcd .. | |
354c317e MF |
376 | put bfd.html |
377 | put bfd.pdf | |
1da0b075 | 378 | |
0f38fd87 NC |
379 | cd binutils |
380 | lcd ../../binutils/binutils <=== NB/ Path not like others | |
07233d96 NC |
381 | put * |
382 | cd .. | |
0f38fd87 | 383 | lcd ../doc |
354c317e MF |
384 | put binutils.html |
385 | put binutils.pdf | |
1da0b075 | 386 | |
0f38fd87 | 387 | cd gprof |
07233d96 NC |
388 | lcd ../../gprof/doc/gprof |
389 | put * | |
390 | cd .. | |
391 | lcd ../.. | |
354c317e MF |
392 | put gprof.html |
393 | put gprof.pdf | |
1da0b075 | 394 | |
0f38fd87 | 395 | cd ld |
07233d96 NC |
396 | lcd ../ld/doc/ld |
397 | put * | |
398 | cd .. | |
399 | lcd ../.. | |
354c317e MF |
400 | put ld.html |
401 | put ld.pdf | |
082cbd3b | 402 | |
1da0b075 NC |
403 | lcd ../../gprofng/doc |
404 | put gprofng.html | |
405 | put gprofng.pdf | |
406 | ||
082cbd3b | 407 | Edit the top level binutils index.html file to change the links |
cb6ad9bb | 408 | to point to the new documentation. |
082cbd3b | 409 | |
bf772a1e | 410 | cd ../.. |
04d7fa21 | 411 | get index.html |
082cbd3b NC |
412 | [edit] |
413 | put index.html | |
624a2451 NC |
414 | rm docs |
415 | ln -s docs-2.3x docs | |
082cbd3b NC |
416 | quit |
417 | ||
bf772a1e NC |
418 | Check that the new web page is correct: |
419 | ||
420 | https://sourceware.org/binutils/ | |
421 | ||
9a5db26e | 422 | For the www.gnu.org site you have to email webmasters@gnu.org |
bf772a1e NC |
423 | and ask them to make the change(s): |
424 | --------------------------------------- | |
425 | Hi FSF Webmasters, | |
426 | ||
427 | Please could the GNU Binutils webpage at: | |
428 | ||
429 | https://www.gnu.org/software/binutils/binutils.html | |
430 | ||
431 | be updated to indicate that there is now a newer version available | |
432 | (2.3x). I have already updated the related page on the sourceware | |
433 | website so this might be useful as a template: | |
434 | ||
435 | https://sourceware.org/binutils/ | |
436 | ||
437 | Thanks very much. | |
438 | ||
439 | Cheers | |
440 | -------------------------------------- | |
9a5db26e | 441 | |
6cb624f8 | 442 | 30. Send emails to binutils@sourceware.org, info-gnu@gnu.org and |
9a5db26e | 443 | David Edelsohn <dje.gcc@gmail.com> announcing the new release. |
03d0d46a NC |
444 | Sign the email and include the checksum: |
445 | ||
9b351c9b | 446 | sha256sum binutils-2.3*.tar.* |
03d0d46a | 447 | |
9a5db26e NC |
448 | (The email to Davis is so that he can update the GNU Toolchain |
449 | social media). Something like this: | |
082cbd3b | 450 | ----------------------------------------------------------------------- |
9a5db26e NC |
451 | Hi Everyone, |
452 | ||
04d7fa21 | 453 | We are pleased to announce that version 2.3x of the GNU Binutils project |
9a5db26e NC |
454 | sources have been released and are now available for download at: |
455 | ||
456 | https://ftp.gnu.org/gnu/binutils | |
457 | https://sourceware.org/pub/binutils/releases/ | |
458 | ||
459 | checksums: xxxx | |
94c2436b | 460 | |
cb6ad9bb NC |
461 | This release contains numerous bug fixes, and also the |
462 | following new features: | |
78b2179a | 463 | |
9a5db26e | 464 | <extract info from the NEWS files> |
94c2436b | 465 | |
e838f9c2 NC |
466 | For more information see: |
467 | ||
468 | https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gas/NEWS;;hb=refs/tags/binutils-2_39 | |
469 | https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=ld/NEWS;hb=refs/tags/binutils-2_39 | |
470 | https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_39 | |
471 | ||
cb6ad9bb NC |
472 | Our thanks go out to all of the binutils contributors, past and |
473 | present, for helping to make this release possible. | |
94c2436b | 474 | |
082cbd3b | 475 | ----------------------------------------------------------------------- |
94c2436b | 476 | |
04d7fa21 NC |
477 | 31. Clean up the source tree: |
478 | ||
479 | git clean -fdx . | |
082cbd3b NC |
480 | |
481 | 32. Edit bfd/development.sh on the branch and set the development flag | |
482 | to "true". (Leave the experimental flag set to "false"). Also bump | |
483 | the version in bfd/version.m4 by adding a trailing .0, so that the | |
484 | date suffix keeps the version lower than the trunk version. | |
485 | Regenerate files. Commit these changes. | |
6cb624f8 | 486 | |
04d7fa21 | 487 | 33. Email the binutils list telling everyone that the 2.3x branch |
bf772a1e | 488 | is now open for business as usual and that patches no longer |
6cb624f8 | 489 | need special approval. |
2012bf01 | 490 | |
cb6ad9bb NC |
491 | 34. Examine the bfd/config.bfd file in the mainline sources and move |
492 | any pending obsolete targets into the definitely obsolete | |
493 | section. Create a changelog entry and commit. | |
a315d390 NC |
494 | |
495 | ||
496 | ||
497 | ||
cb6ad9bb | 498 | -------------------------------------------------------------------------- |
a315d390 | 499 | How to perform a POINT release. |
cb6ad9bb | 500 | -------------------------------------------------------------------------- |
78b2179a NC |
501 | |
502 | A point release is easier than a normal release since a lot of the | |
503 | work has already been done. The branch has been created, the | |
504 | translations updated and the documentation uploaded. So the procedure | |
505 | looks like this: | |
506 | ||
507 | 0. Decide that a point release is necessary. | |
508 | ||
509 | Usually this only happens when a sufficient number of serious | |
510 | bugs have been found and fixed since the previous release, and a | |
511 | new official release is not imminent. | |
512 | ||
513 | 1. Tell the community that a point release is happening. Ask | |
514 | maintainers to ensure that their ports are up to date on the | |
515 | release branch. Ask the community if there are any bug fixes | |
516 | which are missing from the branch. Allow some time for the | |
517 | responses to this step. | |
518 | ||
519 | 2. Make sure that the branch sources build, test and install | |
520 | correctly. | |
521 | ||
98ab9e96 NC |
522 | 2.5 Prepare a list of the bugs which have been fixed. This |
523 | will be needed for step 8. | |
a960d29f | 524 | |
ef336cb0 | 525 | 3. In the branch sources: |
a960d29f | 526 | |
ef336cb0 | 527 | a. Update the minor release number in bfd/version.m4. |
04d7fa21 | 528 | b. Edit bfd/development.sh, set "development=false". |
ef336cb0 | 529 | c. Regenerate the configure files. |
72a51a06 | 530 | d. Remove spurious autom4te.cache files: |
442a6ce8 | 531 | |
72a51a06 | 532 | git clean -fdx |
442a6ce8 | 533 | |
72a51a06 | 534 | e. Commit the updates along with a "this-is-the-2.3x.y-release" |
ef336cb0 | 535 | note in all of the changelogs. |
72a51a06 | 536 | f. Tag the branch with the new release number: |
ef336cb0 | 537 | |
04d7fa21 | 538 | git tag -a binutils-2_3x_y |
ef336cb0 | 539 | [optional: add "-u XXXXX" to sign with a gpg key] |
04d7fa21 | 540 | git push origin binutils-2_3x_y |
ef336cb0 | 541 | |
72a51a06 NC |
542 | g. Check that your file creation mask will create the |
543 | correct file permissions. Ie: | |
8071ec09 NC |
544 | |
545 | umask 022 | |
a960d29f | 546 | |
72a51a06 | 547 | h. Create the release tarballs: |
04d7fa21 | 548 | |
ef336cb0 | 549 | ./src-release -b -g -l -x binutils |
8071ec09 | 550 | |
72a51a06 | 551 | i. Check that the files in the tarballs have the correct |
8071ec09 | 552 | permissions. |
a960d29f | 553 | |
72a51a06 NC |
554 | j. Clean the source tree again |
555 | ||
556 | git clean -fdx | |
557 | ||
558 | k. Edit bfd/development.sh and set "development=true". | |
559 | l. Commit this change. | |
78b2179a | 560 | |
ef336cb0 NC |
561 | 4. [If paranoid - upload the tarballs to one of the FTP servers and |
562 | ask people to test it before going on to step 5]. | |
a960d29f | 563 | |
ef336cb0 | 564 | 5. Upload the tarballs to ftp.gnu.org. |
78b2179a | 565 | |
72a51a06 | 566 | gnupload --to ftp.gnu.org:binutils binutils-*.tar.* |
78b2179a | 567 | |
ef336cb0 | 568 | The gnupload script is in the gnulib/build-aux directory. |
78b2179a | 569 | |
ef336cb0 | 570 | 6. Upload the tarballs to sourceware.org: |
78b2179a NC |
571 | |
572 | sftp sourceware.org | |
442a6ce8 | 573 | cd /sourceware/ftp/pub/binutils/releases |
72a51a06 NC |
574 | put binutils-*.tar.* |
575 | chmod 644 binutils-*.tar.* | |
78b2179a NC |
576 | quit |
577 | ||
442a6ce8 | 578 | It is OK to upload the signatures as well. |
78b2179a | 579 | |
ef336cb0 | 580 | 7. Update web pages. For sourceware.org: |
78b2179a NC |
581 | |
582 | * Log on to sourceware.org | |
442a6ce8 | 583 | * Go to /sourceware/www/sourceware/htdocs/binutils |
72a51a06 | 584 | * Edit index.html and update the latest release number (if this is a latest release) |
78b2179a NC |
585 | |
586 | For the www.gnu.org site you have to email webmasters@gnu.org | |
587 | and ask them to make the change(s). | |
588 | ||
ef336cb0 NC |
589 | 8. Send an emails to the binutils list, info-gnu@gnu.org and |
590 | David Edelsohn <dje.gcc@gmail.com> announcing the new release. | |
591 | (The email to Davis is so that he can update the GNU Toolchain | |
592 | social media). Something like this: | |
03d0d46a | 593 | |
78b2179a NC |
594 | ------------------------------------------------------------------------ |
595 | Hi Everyone, | |
596 | ||
04d7fa21 | 597 | We are pleased to announce that version 2.3x.y of the GNU Binutils |
442a6ce8 | 598 | project sources have been released and are now available for download at: |
a960d29f | 599 | |
78b2179a NC |
600 | https://ftp.gnu.org/gnu/binutils |
601 | https://sourceware.org/pub/binutils/releases/ | |
602 | ||
04d7fa21 | 603 | This is a point release over the previous 2.3x version, containing bug |
78b2179a NC |
604 | fixes but no new features. |
605 | ||
606 | Our thanks go out to all of the binutils contributors, past and | |
607 | present, for helping to make this release possible. | |
98ab9e96 NC |
608 | |
609 | Here is a list of the bugs that have been fixed: | |
610 | xx | |
611 | xx | |
612 | xx | |
613 | xx | |
78b2179a | 614 | -------------------------------------------------------------------------- |
a315d390 NC |
615 | |
616 | 9. Create a new Bugzilla entry for the point release. | |
617 | ||
618 | https://sourceware.org/bugzilla/editversions.cgi?product=binutils | |
619 | ||
620 | And a new milestone too: | |
621 | ||
622 | https://sourceware.org/bugzilla/editmilestones.cgi?product=binutils | |
78b2179a | 623 | \f |
a2c58332 | 624 | Copyright (C) 2017-2022 Free Software Foundation, Inc. |
78b2179a NC |
625 | |
626 | Copying and distribution of this file, with or without modification, | |
627 | are permitted in any medium without royalty provided the copyright | |
628 | notice and this notice are preserved. |