Date: 16 Mar 2002 16:43:47 +0200 From: Maxim Sobolev <sobomax@mail.ru> To: re@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: -CURRENT Feature Slush is OVER Message-ID: <1016289691.91096.2.camel@notebook> In-Reply-To: <20020316111818.GO17499@freebsdmall.com> References: <20020316111818.GO17499@freebsdmall.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, 2002-03-16 at 13:18, Murray Stokely wrote: > Thanks for your cooperation in keeping -CURRENT relatively stable > over the past week. Due to a request from the CVS administrators, we > are performing the code branch in the Perforce depot under > //depot/releng/5_dp1/. Commits to this Perforce branch require re@ > approval. > > This is not going to be a supported branch. It is solely a work > area for the release engineers to tweak the release documentation, > back out recent problematic changes, merge in a conservative set of > new changes, and otherwise perform quality assurance work. Our two > primary goals in all of this are (1) to provide a usable preview of > the 5.0-CURRENT code, and (2) to minimize the impact on -CURRENT > developers. After evaluating several different options, using > Perforce was deemed the best tool for the job. Could we have commit logs from the commits into that branch be sent to cvs-all@, because otherwise most of the developers would be unable to see what's going on there, which IMO is not a good thing. Thanks! -Maxim [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQA8k1mboNu5t4iCBa8RAtjBAJ9Jjejvzit4i1ACfmrGWbNGvioNPgCcDgNu mH+HxvXLxFW7SW0zywLUu9Q= =hVHq -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1016289691.91096.2.camel>