Return-Path: 
 <commons-dev-return-45308-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 66646 invoked from network); 7 Feb 2004 22:21:46 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 7 Feb 2004 22:21:46 -0000
Received: (qmail 50017 invoked by uid 500); 7 Feb 2004 22:21:30 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 49974 invoked by uid 500); 7 Feb 2004 22:21:28 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 49953 invoked from network); 7 Feb 2004 22:21:28 -0000
Received: from unknown (HELO smtp-out2.blueyonder.co.uk) (195.188.213.5)
  by daedalus.apache.org with SMTP; 7 Feb 2004 22:21:28 -0000
Received: from [10.0.0.2] ([82.38.65.173]) by smtp-out2.blueyonder.co.uk with
 Microsoft SMTPSVC(5.0.2195.5600);
	 Sat, 7 Feb 2004 22:21:33 +0000
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <4025595A.6030902@latte.harvard.edu>
References: <Pine.LNX.4.44.0402071508110.13744-100000@umbongo.flamefew.net>
 <40255043.9090103@latte.harvard.edu>
 <0A80190A-59B2-11D8-A1A4-003065DC754C@blueyonder.co.uk>
 <4025595A.6030902@latte.harvard.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FB9464DF-59BB-11D8-A1A4-003065DC754C@blueyonder.co.uk>
Content-Transfer-Encoding: 7bit
From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
Subject: Re: [general] Maven 'LATEST-RELEASE' tag suggestion
Date: Sat, 7 Feb 2004 22:21:32 +0000
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
X-Mailer: Apple Mail (2.612)
X-OriginalArrivalTime: 07 Feb 2004 22:21:33.0609 (UTC)
 FILETIME=[BE28C190:01C3EDC8]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N


On 7 Feb 2004, at 21:32, Mark R. Diggory wrote:

> robert burrell donkin wrote:
>
>> On 7 Feb 2004, at 20:53, Mark R. Diggory wrote:
>> <snip>
>>> It also gives developers some room to work. If there is a global 
>>> nightly/weekly process for generating the commons site and its 
>>> sub-projects then in reality they probibly don't want the site 
>>> xref/xdocs generated off of thier bleeding edge all the time.
>> hmmm...
>> i'd probably want the best of both worlds - the latest and greatest 
>> version but also versions of the site for each release. i suppose 
>> that it'd be possible to do something with directories so 
>> commons/kool/current would contain the latest version but 
>> commons/kool/7.12.89/ would contain the documentation which was 
>> current when 7.12.89 was released.
>> just a suggestion (rather than a criticism)...
>> - robert
>
> No, thats a really good point about versioned javadoc. Javadoc for 
> version 1.0, 2.0, ..., Current of a subproject.
>
> This would require maintaining the content of previous release site 
> generations, pushing into a special directory reserved for its 
> archiving.

craig advocated something similar in the original commons release 
documents (but only kept the last release). it shouldn't be too great a 
burden to copy the current website into a specially numbered directory 
when a release is cut.

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org