This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: The 2.20 release code freeze is very near


On 03/07/14 02:55, Roland McGrath wrote:
>> The code freeze for the glibc-2.20 release was scheduled for July 1st.
>> I realise there are still a few things that have appeared on the mailing
>> list that are desirable for this release as listed on the wiki page [1].
>>
>> So this is not a freeze, but it should be getting quite cold...
>> Consider whether your changes can wait until 2.21.
> 
> Another thing to consider is that (according to his autoresponder), Joseph
> is unavailable until July 15th.  Shortly after that, it's Cauldron and
> several of us will be travelling and so on.  (Myself, I will be travelling
> after the 16th, then at Cauldron, and then on vacation the following week,
> until the 28th).

Thanks for that information. I had forgotten about Cauldron.

> People being gone certainly doesn't mean we should have more destabilizing
> changes than we would if everyone were around.  But it does mean that the
> testing by machine maintainers, maintainer review of small patches, and so
> forth, will be delayed or slowed down this month.
> 
> I don't think we should get upset about delays, really.  The notion of
> time-based releases is to make sure we have them frequently enough, not
> because we have deadlines.  It's more important that we have a release
> of high quality and are confident of the testing it's received than that
> it happen in a given month rather than the next.

I agree.  I see it as my role to start pushing people towards the
release now anyway to stop the release delay being months rather than weeks.

Allan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]