Closing glibc release branches 2.18 - 2.24.

Carlos O'Donell carlos@redhat.com
Thu Mar 26 20:35:50 GMT 2020


On 3/26/20 4:32 PM, Carlos O'Donell wrote:
> Community,
> 
> Given the information on the Release page here:
> https://sourceware.org/glibc/wiki/Release/
> 
> I would like to close the following branches to fixes:
 
release/2.18/master
release/2.19/master
release/2.20/master
release/2.21/master
release/2.22/master
release/2.23/master
release/2.24/master
 
And this time without accidentally hitting send...

I would like to limit the depth to which we should be
backporting CVE fixes.

Debian 10, buster, is using glibc 2.29, so I think closing
this to 2.24 is OK.

Tulio,

Can you please confirm the status of IBM AT?

Are you still supporting 2.24 and 2.26?

If you're not then we could possibly close those branches
also, and that means closing all branches released before
2017.

-- 
Cheers,
Carlos.



More information about the Libc-alpha mailing list