This is the mail archive of the
mailing list for the glibc project.
Re: 2.26 freeze in a little over a week
- From: Palmer Dabbelt <palmer at dabbelt dot com>
- To: siddhesh at gotplt dot org
- Cc: szabolcs dot nagy at arm dot com
- Cc: nd at arm dot com
- Cc: Andrew Waterman <andrew at sifive dot com>
- Cc: Darius Rad <darius at bluespec dot com>
- Cc: libc-alpha at sourceware dot org
- Cc: carlos at redhat dot com
- Date: Thu, 22 Jun 2017 11:38:49 -0700 (PDT)
- Subject: Re: 2.26 freeze in a little over a week
- Authentication-results: sourceware.org; auth=none
On Thu, 22 Jun 2017 11:37:27 PDT (-0700), email@example.com wrote:
> 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.
OK, thanks! We're pushing on the test suite right now, and we'll try to get
another patch set out in the next few days so we can see where we stand.