Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Joel Brobecker <brobecke@adacore.com>, gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 17 release schedule proposal
Date: Mon, 28 Apr 2025 13:17:43 +0200	[thread overview]
Message-ID: <00bf8449-077b-444c-9d34-be8f777531f6@suse.de> (raw)
In-Reply-To: <aA0ppp2aeRmfZgf6@adacore.com>

On 4/26/25 20:44, Joel Brobecker wrote:
> Hello everyone,
> 
> Now that the GDB 16.3 release is out, it's time to start thinking
> about the GDB 17.x release cycle.
> 
> Here are the dates I propose we aim for:
> 
>    * Branching: Jun 21st
>    * Release: Jul 26th
> 
> This is only 2 months away from the last release, so slightly
> on the fast side, but it has the advantage of reducing our overlap
> with the month of Aug, which is typically very slow. It also helps
> keep the one major release every 6 months pace.
> 
> Let us know if you'd prefer some different dates.
> 
> And as always, please let us know if there are some pending issues
> or changes that you think should make it to release 17 (with
> a rationale for the suggestion please :-) ).

Hi Joel,

I think we should fix PR32167 ( 
https://sourceware.org/bugzilla/show_bug.cgi?id=32167 ).

The problematic behaviour is that gdb hangs sometimes after the user 
presses ^C.  This may be a regression introduced in gdb 15.1.

I've already updated the target milestone of the PR to 17.1.

Thanks,
- Tom


  reply	other threads:[~2025-04-28 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26 18:44 Joel Brobecker
2025-04-28 11:17 ` Tom de Vries [this message]
2025-04-28 14:29   ` Joel Brobecker
2025-05-24 16:28   ` Joel Brobecker
2025-05-25  7:04     ` Tom de Vries
2025-04-28 14:32 ` 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=00bf8449-077b-444c-9d34-be8f777531f6@suse.de \
    --to=tdevries@suse.de \
    --cc=brobecke@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