Hi All,
Having now done a release, I have a couple of suggestions/questions
about the release procedure.
===
The dist directories currently have symbolic links named ..current..
that point to the actual files in the binary and source subdirs.
Is there actually any justification for keeping
On 6/12/05, Simon Kitching [EMAIL PROTECTED] wrote:
Hi All,
Having now done a release, I have a couple of suggestions/questions
about the release procedure.
===
The dist directories currently have symbolic links named ..current..
that point to the actual files in the binary and source
On Sun, 2005-06-12 at 18:32 -0700, Martin Cooper wrote:
On 6/12/05, Simon Kitching [EMAIL PROTECTED] wrote:
Hi All,
Having now done a release, I have a couple of suggestions/questions
about the release procedure.
===
The dist directories currently have symbolic links named
On 5/21/05, Stephen Colebourne [EMAIL PROTECTED] 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
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:
-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
Hi,
Section #15 of the release page has me puzzled:
http://jakarta.apache.org/commons/releases/release.html
What's the point of the first update links bits, and how does this
interact with how maven generates the component's website?
Thanks,
Simon
