GDB 17 release schedule proposal

GDB 17 release schedule proposal

[Joel Brobecker]

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 :-) ).

Thank you all!
-- 
Joel

Re: GDB 17 release schedule proposal

[Tom de Vries]

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

Re: GDB 17 release schedule proposal

[Joel Brobecker]

> 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 for the update, Tom, and for updating the target milestone.
Good luck!

-- 
Joel

Re: GDB 17 release schedule proposal

[Luis Machado]

Hi Joel,

On 4/26/25 19: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.

Thanks for getting that release out.

> 
> 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 :-) ).
> 
> Thank you all!

The dates for gdb 17 look good to me.

Re: GDB 17 release schedule proposal

[Joel Brobecker]

Hi Tom,

> 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.

Just checking in in the status of this issue that you identified for
release 17. Has there been some progress on it?

Thank you!
-- 
Joel

Re: GDB 17 release schedule proposal

[Tom de Vries]

On 5/24/25 18:28, Joel Brobecker wrote:
> Hi Tom,
> 
>> 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.
> 
> Just checking in in the status of this issue that you identified for
> release 17. Has there been some progress on it?

Hi Joel,

the last comment of the PR lists a solution that works on Linux (well, 
at least for the test-case, at this point I can't remember whether I 
tested it on the entire testsuite): using kill.

But I'm not sure whether that's available on other OSes.

I got distracted by other things, I'll try to find time to get back to 
this PR.

Thanks,
- Tom

> Thank you!