Date: Tue, 29 Jan 2002 20:41:43 -0800 From: Jordan Hubbard <jkh@winston.freebsd.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: obert Watson <rwatson@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, re@FreeBSD.org Subject: Re: cvs commit: src/etc master.passwd Message-ID: <64119.1012365703@winston.freebsd.org> In-Reply-To: Message from Ruslan Ermilov <ru@FreeBSD.org> of "Tue, 29 Jan 2002 16:40:06 %2B0200." <20020129164006.B61992@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I think it's really easy to answer this question: There is not now, nor has there ever been, such a thing as an "automatic unfreeze". Your assumption should *always* be that a previously announced freeze is in effect up until the point where you receive explicit confirmation that the freeze is over from whatever *meisters have frozen the tree in question (doc, ports, src). That's the way it always has been, that's the way it is now, that's the way it's likely to be for the foreseeable future, and that's all there is to it. :) - Jordan > On Tue, Jan 29, 2002 at 09:13:11AM -0500, obert Watson wrote: > > > > On Tue, 29 Jan 2002, Ruslan Ermilov wrote: > > > > > On Tue, Jan 29, 2002 at 09:03:54AM -0500, Robert Watson wrote: > > > > Was this approved by re@? > > > > > > It was my understanding from reading logs for CVSROOT/avail that since > > > RELENG_4_5 branch was created and RELENG_4_5_0_RELEASE tag was laid > > > down, the commits to the RELENG_4 branch do not require a re@ approval > > > anymore, no? > > > > If there has not been an announcement saying the tree has unfrozen, then > > it's still frozen. We've made the decision to keep the RELENG_4 branch > > frozen until the release is actually cut, so that we can keep RELENG_4 in > > sync if there are last minute commits to support the release effort. The > > RELENG_4_5_0_RELEASE tag should be considered mutable until the release > > itself is announced. Please back your commit out until you see an > > announcement to the contrary regarding the code freeze. > > > I'm sorry about this and will back my change out in 30 minutes or > after I see the reply to the below (whatever happens earlier), but > could you please clarify something for me and others: > > 1. What was the point in creating RELENG_4_5 branch if RELENG_4 is > still frozen? I thought that creating RELENG_4_5 branch would > automatically unlock RELENG_4. At least, that's the feeling > I've got from reading releng.html, and this is the way it worked > before. > > 2. There were two simultaneous commits to the RELENG_4 and RELENG_4_5 > branches for gnu/usr.bin/groff/tmac/mdoc.local by murray, and only > RELENG_4_5 commit was marked as being ``Approved by: re'', in > support of my feeling. > > 3. I saw multiple commits to the RELENG_4 branch of src/UPDATING by > imp without the ``Approved by: re'' bit that also support my > feeling. > > > Cheers, > -- > Ruslan Ermilov Sysadmin and DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64119.1012365703>