This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: 2.29 hard freeze
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh at sourceware dot org>, GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Sun, 27 Jan 2019 21:47:19 -0500
- Subject: Re: 2.29 hard freeze
- References: <b4dd317e-8dba-9a9c-5b70-7aa59f964639@sourceware.org>
On 1/27/19 11:32 AM, Siddhesh Poyarekar wrote:
> Hello folks,
>
> There's less than a week to go for the scheduled release date, i.e. 1
> Feb 2019, and I need these last 4 days to run tests, tag the release,
> sacrifice chickens to please the release gods, etc. so master is now in
> a hard freeze. Please do not push anything into master for the next 4
> days; if something needs to urgently go in then please cc me with an
> explanation of why the fix is necessary (badly broken build, 0-day sev-1
> security bug fix, etc.).
>
> See y'all on the other side of the release. Until then, please
> contribute to the plan for the ChangeLog automation script so that we
> can stop writing ChangeLogs in 2.30 and beyond.
I had problems with my b-m-g builds, but the last rwlock fix looks good.
I don't have to push this for the release, it can wait until after the
release and then get backported to the stable branch. So lets start
the final testing without it for now.
--
Cheers,
Carlos.