This is the mail archive of the
mailing list for the glibc project.
Re: 2.26 freeze in a little over a week
- From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- To: Palmer Dabbelt <palmer at dabbelt dot com>, szabolcs dot nagy at arm dot com
- Cc: nd at arm dot com, Andrew Waterman <andrew at sifive dot com>, Darius Rad <darius at bluespec dot com>, libc-alpha at sourceware dot org, carlos at redhat dot com
- Date: Fri, 23 Jun 2017 00:07:27 +0530
- Subject: Re: 2.26 freeze in a little over a week
- Authentication-results: sourceware.org; auth=none
- References: <mhng-b49e15b1-af53-4cf6-9246-f8c7c2ab1b14@palmer-si-x1c4>
On Thursday 22 June 2017 11:18 PM, Palmer Dabbelt wrote:
> We're not upstream in Linux yet, we're also in the process of submitting
> patches. We've been through two rounds of review of the ABI on the Linux
> mailing list and there weren't any comments the second time.
> We've committed to maintaining ABI stability with the first one to get released
> (which would be glibc if we can get into 2.26).
We usually wait for the kernel bits to go in before releasing a glibc
with the new ABI, but I'll defer to Carlos, Joseph, etc. on that.
Provided that is clear, I think it should be safe to continue reviewing
the patchset until about a week or two before the release date
(tentatively 1 Aug) and then take a call on whether it is ready or needs
to be pushed to 2.27. Given that it does not interact with other
architecture code, their testing should not get affected.