starting the GDB 14 release process

starting the GDB 14 release process

[Joel Brobecker]

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!
-- 
Joel

Re: starting the GDB 14 release process

[Luis Machado]

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

Re: starting the GDB 14 release process

[Joel Brobecker]

Hi Luis,

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

OK.

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

PRs are not requirements for this stage, but they do make it a lot easier
for me to keep track of the status, especially if you remember to use
those PRs in the commit message, and also if you cross-ref discussions
in the PR. So, if it's not too much extra work for you, that would be
super useful.

-- 
Joel

Re: starting the GDB 14 release process

[Luis Machado]

Hi,

On 7/26/23 16:26, Joel Brobecker wrote:
> Hi Luis,
> 
>> Although not a blocker for the release, I'd like to include the
>> AArch64 SME and SME2 support for the GDB 14 release.
> 
> OK.
> 
>> Should I create tickets for those or would this be OK to track less
>> formally?
> 
> PRs are not requirements for this stage, but they do make it a lot easier
> for me to keep track of the status, especially if you remember to use
> those PRs in the commit message, and also if you cross-ref discussions
> in the PR. So, if it's not too much extra work for you, that would be
> super useful.
> 

Here it is: https://sourceware.org/bugzilla/show_bug.cgi?id=30689

As the two series get updated, I'll add the PR reference.

Thanks,
Luis

Re: starting the GDB 14 release process

[Tom Tromey]

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

Re: starting the GDB 14 release process

[Joel Brobecker]

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

Makes sense that we'd want those.

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

If you have PRs already, that would indeed be easier to keep track of
status.

Thanks Tom,
-- 
Joel

Re: starting the GDB 14 release process

[John Baldwin]

On 7/5/23 8:23 AM, 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?

I don't have PRs, but I have two series open that I'd like to be in 14.1:

- Handle variable XSAVE layouts
- Fixes for multiprocess for FreeBSD's native target

This latter one does include a fix for PR 21497

I could open a PR for the former for the bug where you can't examine
XSAVE registers (like AVX) from core dumps generated on modern AMD
processors.

-- 
John Baldwin

Re: starting the GDB 14 release process

[Joel Brobecker]

Hi John,

> I don't have PRs, but I have two series open that I'd like to be in 14.1:
> 
> - Handle variable XSAVE layouts
> - Fixes for multiprocess for FreeBSD's native target
> 
> This latter one does include a fix for PR 21497
> 
> I could open a PR for the former for the bug where you can't examine
> XSAVE registers (like AVX) from core dumps generated on modern AMD
> processors.

Thanks for the heads up. What's the ETA for those patches, do you think?

-- 
Joel

Re: starting the GDB 14 release process

[John Baldwin]

On 7/26/23 7:44 PM, Joel Brobecker wrote:
> Hi John,
> 
>> I don't have PRs, but I have two series open that I'd like to be in 14.1:
>>
>> - Handle variable XSAVE layouts
>> - Fixes for multiprocess for FreeBSD's native target
>>
>> This latter one does include a fix for PR 21497
>>
>> I could open a PR for the former for the bug where you can't examine
>> XSAVE registers (like AVX) from core dumps generated on modern AMD
>> processors.
> 
> Thanks for the heads up. What's the ETA for those patches, do you think?

In theory the second series I can push without approval since it is all
FreeBSD-specific and earlier revisions have had some review.  I'm happy
to still get more review, but given some of the cases it fixes (e.g.
being able to debug usefully across a fork when staying attached to
both processes), I'd rather have an imperfect version of it in 14 than
wait to get it completely perfect.

For the XSAVE series, that one is getting useful review feedback from Simon,
and I do have a workaround for the one issue Keith encountered while testing
it.  I do need some resolution for which type of workaround we want to use
though.

-- 
John Baldwin

Re: starting the GDB 14 release process

[John Baldwin]

On 7/26/23 7:44 PM, Joel Brobecker wrote:
> Hi John,
> 
>> I don't have PRs, but I have two series open that I'd like to be in 14.1:
>>
>> - Handle variable XSAVE layouts
>> - Fixes for multiprocess for FreeBSD's native target
>>
>> This latter one does include a fix for PR 21497
>>
>> I could open a PR for the former for the bug where you can't examine
>> XSAVE registers (like AVX) from core dumps generated on modern AMD
>> processors.
> 
> Thanks for the heads up. What's the ETA for those patches, do you think?

FYI, both of these series have landed in master.

-- 
John Baldwin