commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: [doc] release procedure
Date Sun, 22 May 2005 03:45:53 GMT
-----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


Mime
View raw message