Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 32401 invoked from network); 22 May 2005 03:46:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 May 2005 03:46:20 -0000 Received: (qmail 4692 invoked by uid 500); 22 May 2005 03:46:16 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 4540 invoked by uid 500); 22 May 2005 03:46:15 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 4519 invoked by uid 99); 22 May 2005 03:46:15 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mail-08.iinet.net.au (HELO mail.iinet.net.au) (203.59.3.40) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 21 May 2005 20:46:14 -0700 Received: (qmail 753 invoked from network); 22 May 2005 03:46:07 -0000 Received: from unknown (HELO ?10.1.1.3?) (203.206.244.247) by mail.iinet.net.au with SMTP; 22 May 2005 03:46:06 -0000 Message-ID: <42900071.5030308@apache.org> Date: Sun, 22 May 2005 13:45:53 +1000 From: Brett Porter User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [doc] release procedure References: <1116578778.3820.53.camel@localhost.localdomain> <428EF463.4020001@btopenworld.com> In-Reply-To: <428EF463.4020001@btopenworld.com> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephen Colebourne wrote: > They look a bit like something I do on Joda-Time, and vaguely similar to [collections]. > > The basic idea is to link the latest version javadoc to a known fixed URL. To achieve this, each releases javadoc must be uploaded in a directory named api-1.1 or similar. > > Thus your server contains: > api-1.0 (1.0 javadoc) > api-1.1 (1.1 javadoc) > apidocs (SVN latest javadoc) > api (Link to api-1.1) I think this is a good idea, but you probably want to version all of your user's documentation (everything you would include in a downloaded distribution). I agree the default user documentation should be the latest release, with SVN versions and historical versions available under sub directories. Cheers, Brett -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkABxOb5RoQhMkRMRAsq6AJ9zJboHiwdhelPk/gIEzPPiM5v63ACdGCE0 f3jErwrGcbwVzTunScMDu4Y= =Go4l -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org