public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: starting the GDB 14 release process
Date: Wed, 26 Jul 2023 09:36:29 -0600	[thread overview]
Message-ID: <87fs5ak7lu.fsf@tromey.com> (raw)
In-Reply-To: <ZKWK1M+trL1709Ia@adacore.com> (Joel Brobecker via Gdb-patches's message of "Wed, 5 Jul 2023 08:23:00 -0700")

>>>>> "Joel" == Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:

Joel> The first order of business for this is to start collecting the list
Joel> of issues that we think should be blocking for that release (and among
Joel> those, which ones should block the creation of the branch).

I don't have too many, but I'd like to get the minor DAP bug fixes in.
I think they shouldn't affect anything else.

Joel> Are there issues you think should be blocking for 14.1? And if there
Joel> is a Bugzilla PR already, can you provide their PR number?

There are 6 of them ... I can mark the target milestone if that would be
helpful.

Tom

  parent reply	other threads:[~2023-07-26 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 15:23 Joel Brobecker
2023-07-24  8:23 ` Luis Machado
2023-07-26 15:26   ` Joel Brobecker
2023-07-27 12:00     ` Luis Machado
2023-07-26 15:36 ` Tom Tromey [this message]
2023-07-26 15:44   ` Joel Brobecker
2023-07-26 18:31 ` John Baldwin
2023-07-27  2:44   ` Joel Brobecker
2023-07-27 15:43     ` John Baldwin
2023-09-06  2:19     ` John Baldwin

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=87fs5ak7lu.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=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).