From owner-freebsd-current Sun Mar 17 13:11:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0F35A37B404; Sun, 17 Mar 2002 13:11:42 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g2HLBUDA105162; Sun, 17 Mar 2002 16:11:30 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020317083510.A10393@dragon.nuxi.com> References: <20020317083315.GO19657@freebsdmall.com> <20020317094853.8C8AF58D@hcswork.hcs.de> <20020317083510.A10393@dragon.nuxi.com> Date: Sun, 17 Mar 2002 16:11:24 -0500 To: obrien@FreeBSD.ORG, Hellmuth Michaelis From: Garance A Drosihn Subject: Re: HEADS UP: -CURRENT Feature Slush is OVER Cc: re@FreeBSD.ORG, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:35 AM -0800 3/17/02, David O'Brien wrote: >My earlier concerns about the use of Perforce were when a developers >expected other developers to use Perforce for _shared_ development. >Or that tried to claim that their code was "published" if it was >in the Perforce depot on Freefall. Exactly my concerns, too. >In this use of Perforce for a -CURRENT snapshot; I don't see how >people can bitch and bitch about it. No committer or developer >has EVER had CVS "access" or "sight" of the source used in previous >snapshot CDROMs. So people are loosing nothing. Perforce is just >a tool to assist Murray and Co. in making this snapshot CD. I agree completely. I have no concerns about them using perforce in this manner. Whatever makes their lives easier in getting out this "developer's preview" is fine by me. >The other reason to NOT do this in the CVS repository is that it >will help deemphasize that the DP is NOT a RELEASE. People should >not be CVSup'ing hoping to get just that point in time, To speak about my own bias on this process, I agree completely with this sentiment. Four weeks from now, no one should care about the particular second in time they used to create this rough snapshot. I see this as more of a dry run for the *process* of creating a release of 5.0. It will give us a convenient bootstrap CD for those who want to try out 5.0, and who also want a bootable CD to do a clean install of "something in 5.0", because they want to "play with it a little". Anyone who thinks they are going to start tracking current had better *track* current, and not depend on this particular CD. It is not a "release". That describes my opinion on what I expect from this developer's preview. I admit that I am not comfortable with using perforce (or subversion, or ) in some other situations, but I think it is perfectly reasonable in this situation. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message