From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Minor updates to release readme
Date: Fri, 7 Jul 2023 08:39:35 +0000 (GMT) [thread overview]
Message-ID: <20230707083935.CFFC4385C6FE@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=dd78c0a824cae272d3a3eae6c51644e210540e2a
commit dd78c0a824cae272d3a3eae6c51644e210540e2a
Author: Nick Clifton <nickc@redhat.com>
Date: Fri Jul 7 09:39:16 2023 +0100
Minor updates to release readme
Diff:
---
binutils/README-how-to-make-a-release | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 72a7091d3d0..9d1d6af3540 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
reply other threads:[~2023-07-07 8:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230707083935.CFFC4385C6FE@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).