It would have been nice that since ports was also frozen, that folks were notified in STABLE and ANNOUCE as well. I went looking through the archives trying to dig up an announcement of this, and of course, could find any. For those who rely upon CVSuping ports, especially in the case of security fixes (to numerous to name right now), this may have also been a good this to mention to that list as well. Maybe for 5.2 this can be put in the "Things To Do" list for release engineering (I think there used to me a line item where appropriate mailing lists wer notified).
Other than that, keep up the good work... looking forward to a bootable and stable 5.x release for this darned laptop I'm stuck on. :-)
Cheers,
David A. Koran
Scott Long wrote:
All,
My email on Tuesday might have been lost in the noise for many of you,
so I apologize and am resending. To recap, the HEAD code freeze was
extended by three days to allow for some final pending work to be
committed and prepare 5.1 to be a good release. The code freeze will
likely end sometime tomorrow, May 30, after which HEAD will open back
up. We ask that large scale changes still be deferred until after
5.1 is actually released so that any problems can be dealt with. The
release engineering team will send out emails explicitely stating when HEAD has thawed and when large changes like new compilers and
dynamic-linked worlds can go it.
Also as a reminder, ***if you have patches that have been approved for
commit, but you have not committed them yet, please do so as soon as
possible***. We want to make a very positive splash with 5.1 since
it is being released right before USENIX ATC and will have working
KSE and 1:1 threads. We appreciate all of the hard work and patience
that everyone has given!
The Release Engineering Team
-------- Original Message -------- Subject: [Fwd: cvs commit: www/en/releases/5.1R schedule.sgml] Date: Tue, 27 May 2003 14:16:39 -0600 From: Scott Long <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
All,
As noted below, the release engineering team has decided to delay the RELENG_5_1 branch by three days in order to allow time for a few more items on the TODO list to be addressed. We apologize for the slip, but feel that it is neccessary to make 5.1 be a good release.
The Release Engineering Team
-------- Original Message -------- Subject: cvs commit: www/en/releases/5.1R schedule.sgml Date: Tue, 27 May 2003 13:11:39 -0700 (PDT) From: Scott Long <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
scottl 2003/05/27 13:11:39 PDT
FreeBSD doc repository
Modified files:
en/releases/5.1R schedule.sgml
Log:
Update the schedule to reflect slipping the branch by three days. We are
almost there, just need a clean up a few things.
Revision Changes Path 1.10 +14 -14 www/en/releases/5.1R/schedule.sgml
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
