Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49504 invoked from network); 19 Aug 2004 11:58:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Aug 2004 11:58:19 -0000 Received: (qmail 63480 invoked by uid 500); 19 Aug 2004 11:58:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63407 invoked by uid 500); 19 Aug 2004 11:58:18 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Derby Development" Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 63396 invoked by uid 99); 19 Aug 2004 11:58:18 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=LINES_OF_YELLING X-Spam-Check-By: apache.org Received: from [204.146.167.214] (HELO Boron.MeepZor.Com) (204.146.167.214) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 19 Aug 2004 04:58:16 -0700 Received: from [192.168.23.5] (dsl093-240-231.ral1.dsl.speakeasy.net [66.93.240.231]) by Boron.MeepZor.Com (8.11.6/8.11.6) with ESMTP id i7JBwEG05962; Thu, 19 Aug 2004 07:58:14 -0400 Message-ID: <412495C8.7030003@Golux.Com> Date: Thu, 19 Aug 2004 07:58:00 -0400 From: Rodent of Unusual Size Organization: The Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: derby repository structure X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- the svn repository for the derby project has been prepared, but it might not have an optimal structure. no code has been imported yet, just pages for the web site. according to the svn people, 'best practice' is for there to be three areas in each versionable module; one for the main-line development (called 'trunk'), one for branches (called, curiously enough, 'branches'), and one for tagged versions. so for module foo, with a single file 'file.name' and a single branch 'B1', the module layout would look something like: /repos/foo/tags /repos/foo/branches/B1/file.name /repos/foo/trunk/file.name the derby project has at least two discrete parts: derby itself, and the site web pages. currently the module is set up (with prefix '/repos/asf/incubator/') as: derby/code/{trunk,tags,branches} derby/site/{trunk,tags,branches} some questions have been raised about whether this is the best structure; an alternative would be: derby/{trunk,tags,branches}/ derby/{trunk,tags,branches}/site making the site just another piece of the overall project. which layout do you think is better? everything *can* be rearranged after the code upload, but it would be a lot simpler if any structural changes were made before then. :-) the only thing that would need to be moved about would be the existing site docco, and it's simply a matter of moving a directory (essentially). - -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQSSVxprNPMCpn3XdAQEsOAP/VKI5XzMrM16H0GRwAuncFIECmSQrqAGK gOo2vS8iwVNU523k8J5tTiahjBRkNjPthStneA29GM3V9Ay1AcyG4Rap/ripxr+Q Cz+yPhqktvx14x8F1dCfYNwIPDT6IkVw/pQkDAVZtDGDCl9KjpcPSLL2n+VbthYA gkWgPRyqIvo= =RhxF -----END PGP SIGNATURE-----