This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Help with 2.15.1 release.
- From: Chris Metcalf <cmetcalf at tilera dot com>
- To: Carlos O'Donell <carlos_odonell at mentor dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, <libc-ports at sourceware dot org>,"Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Thu, 21 Jun 2012 13:36:15 -0400
- Subject: Re: Help with 2.15.1 release.
- References: <4FE32D83.1090909@mentor.com>
On 6/21/2012 10:19 AM, Carlos O'Donell wrote:
> Community,
>
> I need help with the 2.15.1 release, in particular backporting and testing take a lot of time.
>
> I clearly wasn't thinking straight when I thought I could do it all myself.
>
> In light of this less than startling revelation I'm looking for help.
>
> The process I'd like to see should work similar to trunk, but with a little more tracking:
>
> * Backport the patch to 2.15 branch.
> * Test it.
> * Post your results to the BZ issue for the backport request.
I have tested all the 2.15 backport bugs relevant to tile on both tilepro
and tilegx64/tilegx32. I updated bugs 13769, 13770, and 13772 with this
status. I also took the liberty of filing another bug (14279) and marking
it as OK too - this tracks the handful of correctness fixes that have gone
into 2.16 and should go into 2.15.1 as well. (I didn't transition the bugs
to RESOLVED since I assumed that should wait until the commits land on the
branch.)
> * I'll ACK as the branch release manager.
> * You checkin the patch and close the issue.
I assume you mean push to master? Or would you prefer me to put this on a
branch that you can pull?
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com