public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Open master branch for glibc 2.37 development
Date: Sun, 31 Jul 2022 11:39:45 +0000 (GMT)	[thread overview]
Message-ID: <20220731113945.9C8623858CDA@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5fded9c44537283593a7f839347f831e15726572

commit 5fded9c44537283593a7f839347f831e15726572
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Sat Jul 30 15:34:11 2022 -0400

    Open master branch for glibc 2.37 development

Diff:
---
 NEWS      | 23 +++++++++++++++++++++++
 version.h |  4 ++--
 2 files changed, 25 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index f61e521fc8..f9bef48a8f 100644
--- a/NEWS
+++ b/NEWS
@@ -5,6 +5,29 @@ See the end for copying conditions.
 Please send GNU C library bug reports via <https://sourceware.org/bugzilla/>
 using `glibc' in the "product" field.
 \f
+Version 2.37
+
+Major new features:
+
+  [Add new features here]
+
+Deprecated and removed features, and other changes affecting compatibility:
+
+  [Add deprecations, removals and changes affecting compatibility here]
+
+Changes to build and runtime requirements:
+
+  [Add changes to build and runtime requirements here]
+
+Security related changes:
+
+  [Add security related changes here]
+
+The following bugs are resolved with this release:
+
+  [The release manager will add the list generated by
+  scripts/list-fixed-bugs.py just before the release.]
+\f
 Version 2.36
 
 Major new features:
diff --git a/version.h b/version.h
index e211fb4441..dd74787b9e 100644
--- a/version.h
+++ b/version.h
@@ -1,4 +1,4 @@
 /* This file just defines the current version number of libc.  */
 
-#define RELEASE "stable"
-#define VERSION "2.36"
+#define RELEASE "development"
+#define VERSION "2.36.9000"


                 reply	other threads:[~2022-07-31 11: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=20220731113945.9C8623858CDA@sourceware.org \
    --to=carlos@sourceware.org \
    --cc=glibc-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).