Re: glibc 2.30 - 6 days until ABI freeze.

[Carlos O'Donell <carlos@redhat.com>]

On 6/27/19 12:27 PM, Zack Weinberg wrote:
> On Mon, Jun 24, 2019 at 9:45 PM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> If you have posted a patch that changes or adds a new
>> ABI *cough* RISC-V 32-bit *cough* then please consider
>> adding yourself to the "Rlease blockers?" list on the
>> release page:
>>
>> https://sourceware.org/glibc/wiki/Release/2.30#Release_blockers.3F
>>
>> Anyone else with changes should do so also.
> 
> Can I get a quick opinion from you as to whether my "public header
> file hygiene improvements" patchset
> (https://sourceware.org/ml/libc-alpha/2019-06/msg00773.html) is 2.30
> material at this point or whether it should wait for 2.31?

My quick opinion is that this is going to break a bunch of stuff and
that's OK, we'll fix the fallout.

However, that to me means that we should commit it when 2.31 opens,
and *right away* to get 6 months of downstream tumbleweed/rawhide
testing with the changes.

-- 
Cheers,
Carlos.