public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: starting the GDB 14 release process
Date: Mon, 24 Jul 2023 09:23:38 +0100	[thread overview]
Message-ID: <470fa016-2205-f453-c7d7-5d62ea9333d1@arm.com> (raw)
In-Reply-To: <ZKWK1M+trL1709Ia@adacore.com>

Hi Joel,

On 7/5/23 16:23, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
> 
> Time to start the process for the next major release (GDB 14.1).
> 
> The first order of business for this is to start collecting the list
> of issues that we think should be blocking for that release (and among
> those, which ones should block the creation of the branch).
> 
> Are there issues you think should be blocking for 14.1? And if there
> is a Bugzilla PR already, can you provide their PR number?
> 
> Thank you!

Thanks for the heads-up.

Although not a blocker for the release, I'd like to include the AArch64 SME and SME2 support for the GDB 14 release.

Should I create tickets for those or would this be OK to track less formally?

Thanks,
Luis

  reply	other threads:[~2023-07-24  8:23 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 [this message]
2023-07-26 15:26   ` Joel Brobecker
2023-07-27 12:00     ` Luis Machado
2023-07-26 15:36 ` Tom Tromey
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=470fa016-2205-f453-c7d7-5d62ea9333d1@arm.com \
    --to=luis.machado@arm.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).