This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Maintaining 2.12
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: Matt Turner <mattst88 at gmail dot com>, libc-alpha at sourceware dot org, Petr Baudis <pasky at suse dot cz>, roland at redhat dot com, schwab at redhat dot com, ams at gnu dot org, joseph at codesourcery dot com
- Date: Fri, 6 Aug 2010 23:33:41 -0400
- Subject: Re: Maintaining 2.12
- References: <20100513142934.GK16800@machine.or.cz><201007261852.18256.vapier@gentoo.org><AANLkTimWcxfbcgtrz3DjkuM95TMPfCM+wesRE6ZLNj+c@mail.gmail.com><201008061238.37184.vapier@gentoo.org>
On Fri, Aug 6, 2010 at 12:38 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday, August 05, 2010 10:58:25 Matt Turner wrote:
>> On Mon, Jul 26, 2010 at 6:52 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> > On Monday, June 21, 2010 15:00:26 Mike Frysinger wrote:
>> >> so it looks like glibc-2.12 has been branched in git about a week ago.
>> >> ?and it's been about 1.5 months since glibc-2.12 was tagged, and
>> >> fortunately glibc- ports was tagged shortly there after.
>> >>
>> >> will the tarballs be packaged soon now ?
>> >
>> > another month gone by ... are we going back to the system where distros
>> > have to roll their own tarballs ?
>>
>> There are glibc-2.12.1 tarballs on ftp.gnu.org/gnu/glibc/ as of Aug 3.
>> Never saw any announcement though.
>
> thanks, i hadnt noticed. ?ive updated the main arches to glibc-2.12.1 in
> Gentoo, but now i just have to wait for someone to make a ports tarball ...
Have we ever made any policy for ports?
Should there be a role of "release manager" for ports releases,
someone to herd the cats into getting "release ready?" Someone to spin
a matching tarball?
Speaking from experience, if I don't know the answer then it means we
haven't talked about it enough, and we haven't done it enough times to
remember what we're supposed to be doing.
Cheers,
Carlos.