From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: stable branches update
Date: Sat, 01 Jul 2023 12:21:20 +0200 [thread overview]
Message-ID: <3745646.kQq0lBPeGt@nimes> (raw)
Hi,
I updated the branches stable-202207 and stable-202301 with the bug fixes
from the last two weeks.
Also, I created a new stable branch stable-202307.
The branch stable-202207 being one year old, it will no longer be updated.
Users of this branch are recommended to switch to stable-202301.
2023-07-01 Bruno Haible <bruno@clisp.org>
doc: Update regarding stable branches.
* doc/gnulib-readme.texi (Stable Branches): Mention new branch
stable-202307. Mention that stable-202207 is no longer updated.
diff --git a/doc/gnulib-readme.texi b/doc/gnulib-readme.texi
index f729bb7fc5..d65360536b 100644
--- a/doc/gnulib-readme.texi
+++ b/doc/gnulib-readme.texi
@@ -580,12 +580,15 @@
documentation updates.
@end itemize
-So far, we have three stable branches:
+So far, we have four stable branches:
@table @code
+@item stable-202307
+A stable branch that starts at the beginning of July 2023.
@item stable-202301
A stable branch that starts at the beginning of January 2023.
@item stable-202207
A stable branch that starts at the beginning of July 2022.
+It is no longer updated.
@item stable-202201
A stable branch that starts at the beginning of January 2022.
It is no longer updated.
next reply other threads:[~2023-07-01 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 10:21 Bruno Haible [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 11:53 stable branches update Bruno Haible
2023-01-01 19:16 Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3745646.kQq0lBPeGt@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).