diff options
| author | Nick Clifton <nickc@redhat.com> | 2023-07-07 09:39:16 +0100 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2023-07-07 09:39:16 +0100 |
| commit | dd78c0a824cae272d3a3eae6c51644e210540e2a (patch) | |
| tree | d03b3cd30643d08751e3cc64ed4f258e894afd5a /binutils | |
| parent | 36b7610ad70d300fd4b76a3ac7a94ff56e23eb7f (diff) | |
| download | gdb-dd78c0a824cae272d3a3eae6c51644e210540e2a.zip gdb-dd78c0a824cae272d3a3eae6c51644e210540e2a.tar.gz gdb-dd78c0a824cae272d3a3eae6c51644e210540e2a.tar.bz2 | |
Minor updates to release readme
Diffstat (limited to 'binutils')
| -rw-r--r-- | binutils/README-how-to-make-a-release | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release index 72a7091..9d1d6af 100644 --- a/binutils/README-how-to-make-a-release +++ b/binutils/README-how-to-make-a-release @@ -34,6 +34,10 @@ How to perform a release. directories and the top level Makefile and configure files. Also consider updating the toplevel libtool files. +------------------------------------------------- +How to create the release branch. +------------------------------------------------- + Approx time to complete from here: 2 hours .... 2.5 If you have not built from the sources recently then now is the @@ -219,9 +223,19 @@ Hi Everyone, architectures... ============================================================================== +============================================================================== + +For the next few weeks, monitor the mailing list for new translations +and respond to any requests to have patches applied to the branch. + +============================================================================== +============================================================================== -When the time comes to actually make the release.... +Then, a couple of weeks later ... +------------------------------------------------- +How to create the release. +------------------------------------------------- 20. Make sure that the branch sources still build, test and install correctly. Make sure that the sources are clean, without any |