2.25 freeze status

[Florian Weimer]

On 01/30/2017 11:25 AM, Phil Blundell wrote:
> On Sat, 2017-01-28 at 19:00 -0500, Carlos O'Donell wrote:
>>
>> Whatever we might think about the seriousness of the issue, it has
>> existed
>> for 4 or 5 releases and few people have run into it, which means we
>> have
>> time to fix it i.e. not a blocker.
>
> That's not an entirely accurate characterisation.  Bug 20019 has indeed
> existed for several releases without anybody noticing, but bug 21041 is
> new.

Phil, thanks for spelling this out explicitly.

> The effect of the older bug 20019 is that affected programs would be at
> risk of crashing if they called longjmp().  But the effect of the newer
> bug 21041 is that such programs cannot start up at all, even if they
> never in fact call longjmp() at runtime.

I share this concern.

Florian