From owner-freebsd-current Tue Feb 26 19:40:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 5855137B400; Tue, 26 Feb 2002 19:40:08 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020227034008.XMJA2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Wed, 27 Feb 2002 03:40:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA97571; Tue, 26 Feb 2002 19:27:33 -0800 (PST) Message-Id: <200202270327.TAA97571@InterJet.elischer.org> Date: Tue, 26 Feb 2002 19:27:32 -0800 (PST) From: Julian Elischer To: Garance A Drosihn Cc: Robert Watson , current@FreeBSD.ORG Subject: Re: Discussion of guidelines for additional version control 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 mechanisms (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 26 Feb 2002, Garance A Drosihn wrote: > At 6:55 PM -0800 2/26/02, Julian Elischer wrote: > > > (1) The timeout begins when contention occurs, of the lock has been > >> declared. This means that if you seriously intend to do some work, > >> you can say "I'm going to do the work", but you don't risk losing the > >> lock until someone comes to you and says "Hey did you ever...". > > > >Locks shouldn't be unilateral and they shouldn't last more that the > >amount of time that it takes to import a change and get it stable. > >i.e. maybe a week or so at most. Someone used KSE-II as an example.. > >They said I had a 2 month lock (??) I don't know where they got that > >idea from.. I had a vague concensus that maybe things may be broken > >for a DAY OR TWO. while the commit was happenning. I the end it was > >about right. > > That would be me... > > I meant "lock" in the sense of expecting no one to make any major > changes in the same area of code. I seem to remember you asking for > such a "lock" (to use the term loosely) in July, and the KSE work > going in around August or so. My memory is admittedly vague. My > point was you explicitly asked for permission to go ahead with that > work, even though (at the time) we were shooting for a release date > in November. > > I don't mean the period of time that -current was actually unstable, > but the amount of time that other developers were asked to stay away > from a major section of code. I never asked for that.. > > -- > 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