Re: One month away from GDB 8.0 branching

[Antoine Tremblay <antoine dot tremblay at ericsson dot com>]

Joel Brobecker writes:

>> > I created a PR for this issue :
>> > https://sourceware.org/bugzilla/show_bug.cgi?id=21169
>> >
>> > I've marked it Target Milestone 8.0
>> >
>>
>> I prefer to fixing this issue in 8.0 too, but to be clear, this is a
>> 7.11 -> 7.12 regression.
>> We changed GDBserver to single step over breakpoint on July 2016, but
>> 7.12 was released on Oct 2016.
>
> That's a very useful piece of information. Thanks, Yao.
>
> Normally, the fact that this isn't a regression is a strong
> indicator that we don't need to block a release pending resolution.
> In this particular case, given the fairly bad effect on the debugging
> session, and the fact that the regression was introduced in our last
> branch, I propose a compromise. We leave it like that for now, and
> will potentially delay the 8.0 release a bit waiting for the fix,
> provided that some one is working on it, and tells us he is close
> to having it. And, come release time, if we the fix is delayed
> to much, or there isn't any news about it, we'll set change
> the target milestone to 8.0.1 and try the same approach (wait a bit
> if there are chances we might get the fix soon).


I'm OK with that however I would like to understand the
release/regression process a bit better that's still a bit new to me.

So this means that regressions do not carry over releases ?

So if an issue is introduced like this one from 7.11 to 7.12 and we
notice it late, and release 7.12 with it, it's not considered a
regression anymore from 7.12 to 8.0 ?

It's just considered a bug ?

Thanks,
Antoine