ABI changes still pending for glibc 2.32?

[Andreas K. Hüttel]

Am Samstag, 4. Juli 2020, 00:24:13 EEST schrieb Carlos O'Donell:
> > Independent of ABI changes, now's probably also a good time to decide
> > about
> > bug 25923, 'Regression: en_US date_fmt and d_t_fmt and "%a %d %b" vs. "%a
> > %b %e"'.
> > 
> > https://sourceware.org/bugzilla/show_bug.cgi?id=25923
> > 
> > Whichever way it goes, the later this is finalized the worse...
> 
> It's on the release blocker list. I'll get this fixed.

Fixed as in

1) follow the slow distros like RHEL, which are two releases behind and can 
still patch it in the release branch without impact to users,

or fixed as in 

2) follow the fast distros like Gentoo, where users have already screamed at 
the maintainers and adapted their scripts (while threatening to switch to 
musl)?

:)

I'm mostly asking because this will have an impact on my policy for Gentoo 
stable. 
If we follow 1), then it would make sense to keep Gentoo stable 2-3 releases 
back (like 2.29) to avoid silliness. 
Current Gentoo stable is 2.30, with 2.31 stabilization pending.


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20200704/996dbb69/attachment.sig>