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