From: Joel Brobecker <brobecker@adacore.com>
To: Jonah Graham <jonah@kichwacoders.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release -- 2019-11-01 Update
Date: Mon, 11 Nov 2019 16:05:00 -0000 [thread overview]
Message-ID: <20191111160506.GA23568@adacore.com> (raw)
In-Reply-To: <CAPmGMvgzEvh4KQNgrxqjHM0yWpwzOUGwWzs4EH+yajfKCkdo0A@mail.gmail.com>
Hi Jonah,
> Can an update be done to the schedule (current/next) at the top of
> https://www.gnu.org/software/gdb/schedule/ please?
Yes, good point. I somehow thought that I had already done that before,
but clearly not. I took this opportunity to include the schedule for
GDB 10 as well, even though it's a bit early to think about it. It's
only tentative, and it's based on making major releases of GDB twice
yearly, minus a month to help avoid slippage over time.
> Also, as an irregular follower of the list and got commits I have noticed
> that we are jumping to 9.x, but is there a 9.0 release, or is the next
> release 9.1?
The release numbering is changing starting with this release cycle.
The 9.0[.x] numbering will be used for the pre-releases, and the first
official release will be 9.1, followed by the corrective release 9.2.
Each new release cycle will then increase the major version, and follow
the same logic as above.
The following wiki page summarizes the process (skip to the diagram
at the end):
https://sourceware.org/gdb/wiki/Internals%20Versions
--
Joel
next prev parent reply other threads:[~2019-11-11 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:16 Joel Brobecker
2019-11-04 21:02 ` Philippe Waroquiers
2019-11-11 17:44 ` Joel Brobecker
2019-11-04 21:26 ` Jonah Graham
2019-11-11 16:05 ` Joel Brobecker [this message]
2019-11-05 0:14 ` Christian Biesinger via gdb-patches
2019-11-11 17:48 ` Joel Brobecker
2019-11-15 1:21 ` Christian Biesinger via gdb-patches
2019-11-15 2:17 ` Joel Brobecker
2019-11-19 3:02 ` Christian Biesinger via gdb-patches
2019-11-05 20:54 ` Tom Tromey
2019-11-05 21:33 ` Simon Marchi
2019-11-10 22:40 ` Andrew Burgess
2019-11-11 17:50 ` Joel Brobecker
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=20191111160506.GA23568@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jonah@kichwacoders.com \
/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