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