glibc 2.36 - Slushy freeze (3 weeks to release)

[Florian Weimer]

* Xi Ruoyao via Libc-alpha:

> On Tue, 2022-07-12 at 09:33 +0200, Florian Weimer via Libc-alpha wrote:
>
>> Does it really make sense to add a glibc port now if we are going to
>> switch to a different ABI two or three releases from now?  I don't
>> think
>> so.
>
> The Glibc patches under review (and the upstreamed kernel/gcc/binutils
> code) are already using the new ABI.
>
> The "old" ABI was only used by commercial distros for customers who want
> to use LoongArch platforms before all the open source components are
> reviewed and upstreamed properly.  Old ABI will never be a part of
> upstream code.
>
> Once glibc is upstreamed we will consider the ABI stabilized, and start
> to encourage people to use upstreamed ABI.  (Obviously we can't do it
> now: we can't just tell people to "rebuild everything per month".)

Okay, that clarifies that aspect, and addresses my concerns.  Thanks.

Florian