From owner-freebsd-chat@FreeBSD.ORG Wed Jan 7 23:34:06 2004 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E24916A4CE; Wed, 7 Jan 2004 23:34:06 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 193AE43D46; Wed, 7 Jan 2004 23:33:47 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])i087Xe7B033676; Thu, 8 Jan 2004 18:33:40 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.10/8.12.10/Submit) id i087Xenp033675; Thu, 8 Jan 2004 18:33:40 +1100 (EST) (envelope-from peter) Date: Thu, 8 Jan 2004 18:33:40 +1100 From: Peter Jeremy To: freebsd-hackers@freebsd.org, freebsd-chat@freebsd.org Message-ID: <20040108073340.GI25474@server.vk2pj.dyndns.org> References: <3FFC03E5.7010305@iconoplex.co.uk> <200401071429.i07ETZMI068819@grimreaper.grondar.org> <20040107200838.GD86935@freepuppy.bellavista.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040107200838.GD86935@freepuppy.bellavista.cz> User-Agent: Mutt/1.4.1i Subject: Re: Where is FreeBSD going? X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 07:34:06 -0000 On Wed, Jan 07, 2004 at 09:08:38PM +0100, Roman Neuhauser wrote: > The ports freeze seems to last too long with recent releses. Or > maybe it's just I've gotten more involved, but out of the last four > months (2003/09/07-today), ports tree has been completely open > for whopping 28 days. I agree the ports tree has not been completely open for as long as it should be recently. This is due to unforeseen problems that resulted in significant delays for both 4.9-RELEASE and 5.2-RELEASE. It's difficult to see how this could have been handled any better. Hopefully there will be fewer problems with future releases. Non-committers can help here by testing -STABLE and -BETA snapshots more extensively so that more problems are ironed out before the ports tags are laid down. (An alternative might be to delay the ports tagging until later in the release cycle, but I suspect that is just as likely to cause problems by having last minute ports breakages cause delays). > Limitations of CVS don't exactly help either. The fact that you need > direct access to the repository to be able to copy a tree with > history (repocopy) as opposed to this operation being part of the > interface[1], which means being lucky enough to find a committer, > and get them commit the stuff within the blink of an eye ports is > open, further constrains people's ability to work on FreeBSD with > some satisfaction. I'm not sure what is meant by this paragraph. CVS doesn't support renaming files or directories - which can be a nuisance. As used within the Project, "repocopy" means manually copying parts of the repository to simulate file/directory duplication or renaming. This ability is restricted to a very small subset of committers - normal committers have to request repocopies as do non-committers. OTOH, replicating the complete FreeBSD CVS repository is trivial via either CVSup or CTM and both procedures are documented in the handbook. Peter