Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of phil.steitz@gmail.com designates
 64.233.182.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=QLeOK3J8sf/MYTNzt9is6m/Rb/awVUSaOLxsyDVTd1/A8JRzSqMH1A6TqqEybUOkXCCtsWrDbE8bMM8nRUkLRGBT2M0zKtXGz8zreF3Gv1+YuNt/YjUGG4rqwIwglTK4yjsbdL+5nb1pQX2O6unNe+iUrkoQag/0Yt8nJiGp8Ok=
Message-ID: <8a81b4af0605221430j72da3896h5cf95c6fc989ffb2@mail.gmail.com>
Date: Mon, 22 May 2006 14:30:39 -0700
From: "Phil Steitz" <phil.steitz@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [site]Sites for snapshots published
In-Reply-To: <1148332980.4407.31.camel@knossos.elmet>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4737675.1148320172216.JavaMail.jira@brutus>
	 <447206D7.1050505@oliver-heger.de>
	 <1148332980.4407.31.camel@knossos.elmet>

On 5/22/06, robert burrell donkin <robertburrelldonkin@blueyonder.co.uk> wr=
ote:
> On Mon, 2006-05-22 at 20:45 +0200, Oliver Heger wrote:
> > Hi,
> >
> > I just noticed that recently the sites of some components have been
> > deployed directly from their svn trunk. So the sites refer to snapshot
> > versions (e.g. BeanUtils, Configuration, Math, ...). Was this done by
> > intension?
>
> yep - i did it. i went through and changed siteAddress then redeployed
> each site.
>
> please feel free to jump in and redeploy anything that isn't right.
>
> > It might be confusing for users if the sites describe features that are
> > not contained in the latest releases.
>
> IMHO it's a trade off. users get to see all the features that are
> available but have to actively search for documentation related to the
> version they have downloaded.
>
> many components provide link to the released documentation (for example
> http://jakarta.apache.org/commons/logging/) though it would probably be
> a good idea to add an indication on the navigation bar that these
> documents apply to the latest code...

That is a best practice that at least [collections], [math] and [lang]
at least all use.  The important thing is to have the javadoc links
correctly labelled in the nav, so users can find "svn latest" or
"x.y-SNAPSHOT" and clearly distinguish this from the latest (and maybe
some previous) release(s).

Phil

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