public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Updates on GDB 8.3.1 and GDB 9 releases (2019-07-14)
Date: Sun, 14 Jul 2019 17:52:00 -0000	[thread overview]
Message-ID: <20190714175240.GA23822@adacore.com> (raw)

Hi Everyone,

It's been a couple months since we released 8.3 already. Our typical
schedule would be to try to create the corrective release ("re-spin")
in about a month from now. Given that...
  - So far, there is only been one fix pushed to the branch since
    the release; and
  - that a month from now is mid-Aug, which is holiday time for many;
... I purpose we don't do anything until end of Aug...

Depending on when we'd like to have GDB 9 come out, we might even
want to skip 8.3.1 entirely? Personally, I don't mind spending the couple
of hours it takes to create a new release, even if it's for a couple
of patches. But perhaps there'll be more by then too.

Now, switching our attention to GDB 9, looking at the GDB/NEWS file,
there isn't anything super major, but the list is a good size already,
so I think we can start the process anytime that makes sense for us.
For instance, what if we started the stabilization process early
September, with a few to branch sometime around early to mid September.

With that plan, we can hopefully have branching by the GNU Cauldron,
and a release within a month of that, which places the release around
early to mid Oct. That's roughly 5 months after the 8.3 release.

Thoughts?
-- 
Joel

             reply	other threads:[~2019-07-14 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 17:52 Joel Brobecker [this message]
2019-07-16 13:02 ` Tom de Vries
2019-08-12 21:44   ` Sergio Durigan Junior
2019-08-21  9:11     ` [8.3 backport] Adjust i386 registers on SystemTap probes' arguments (PR breakpoints/24541) Tom de Vries
2019-09-04  8:19       ` [PING][8.3 " Tom de Vries
2019-09-04 16:43         ` Sergio Durigan Junior
2019-09-09 20:53           ` Joel Brobecker
2019-09-11 20:11             ` Tom de Vries

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=20190714175240.GA23822@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@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).