public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13.2 and GDB 14 releases...
Date: Sat, 29 Apr 2023 13:15:23 -0700	[thread overview]
Message-ID: <ZE162/x3RNEcKeXH@adacore.com> (raw)

Hi Team,

GDB 13.2 Release:
=================

It's been a little over 2 months since we released GDB 13.1, so
I thought I'd start investigating a possible GDB 13.2 release,
roughly a month from now. I looked at the gdb-13-branch, and
we have a total of 5 changes, all of them sufficiently important
IMO to justify a .2 release. So let's do it, and let's target
end of May for it.

If you guys know of any problem that you think should be fixed in
GDB 13.2, and therefore should block its release, please create
a Bugzilla PR for it, and then set its Target Milestone to 13.2.

As a reminder also: Now that the .1 release has been made, *all*
changes to the gdb-13-branch should be documented via a Buzilla PR.
This is to ensure that, come the time to make the release, the
announcement can include the list of changes brought by the release,
and the links to the corresponding PRs.

GDB 14.1 Branching and Release
==============================

Normally, my default approach is to start talking about the next
major release as soon as the previous .2 release is out. The idea
is to give ourselve 3 months or so to prepare for it, branch and
then release, so as to try to follow a schedule of one major release
every 6 months.

In this case, I think it's too early to tell. I've looked at the NEWS
file, and while there are a number of nice new features, maybe we might
want to wait a little longer to see if we can pack this release a little
more.

Cheers,
-- 
Joel

             reply	other threads:[~2023-04-29 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 20:15 Joel Brobecker [this message]
2023-05-01 13:37 ` Simon Marchi
2023-05-01 14:58   ` Joel Brobecker
2023-05-01 15:15     ` Sam James
2023-05-02  6:55       ` Hector Martin
2023-05-01 16:39     ` Simon Marchi
2023-05-02  9:23     ` Luis Machado
2023-05-01 16:16   ` John Baldwin
2023-05-02 12:57 ` Luis Machado

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=ZE162/x3RNEcKeXH@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).