From dd78c0a824cae272d3a3eae6c51644e210540e2a Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Fri, 7 Jul 2023 09:39:16 +0100 Subject: Minor updates to release readme --- binutils/README-how-to-make-a-release | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) (limited to 'binutils') 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 -- cgit v1.1