Re: glibc 2.24 --- Hard freeze starting

[Adhemerval Zanella <adhemerval dot zanella at linaro dot org>]

On 18/07/2016 06:57, Aurelien Jarno wrote:
> Hi,
> 
> On 2016-07-14 15:35, Adhemerval Zanella wrote:
>> Maintainers,
>>
>> We are now in hard freeze as stated last week (with to days off due some
>> recent fixes).  As before, please keep your commits minimal, documentation
>> changes only, simple bug fixes, and no translatable strings.
>>
>> Please start test your machines, refresh the ULP files and update the 
>> release page [2].
>>
>> Current I see that we have 3 blockers:
>>
>> 1. [BZ #13165] New condition variable: Torvalds, I think you the most
>>    qualified to give us if you think or not this change is safe enough
>>    for 2.24 inclusion or if you prefer to commit in start of 2.25. I do
>>    not have a strong opinion.
>>
>> 2. malloc: Remove malloc_get_state, malloc_set_state: based on recent build
>>    issues with malloc hook change, I would suggest to move this change to
>>    2.25.
>>
>> 3. [PATCH] Fix cos computation for multiple precision fallback (bz #20357):
>>    I plan to review this patch today or tomorrow, but this its straightforward
>>    and contained enough so we can commit.  The only issue I see the possible
>>    need of ULP regeneration in some architectures, so ideally we should push
>>    this by the end of this week.
>>
>> About the security bugs to news, the only one that is not documented in NEWS
>> is BZ#19755 [4].  My understanding is this does not have a CVE assigned, so
>> should we still explicit add it on NEWS?
>>
>> Any other blockers and/or comments?
> 
> Do you think we can get the following patch in this release? It's not
> strictly speaking a regression, but I guess more and more people are
> going to switch to GCC 6 in the next months.
> 
> https://sourceware.org/ml/libc-alpha/2016-07/msg00440.html
> 
> Aurelien
> 

I see these kind of fixes ok for commit while in hard release.