On Wed, 2005-07-20 at 13:54 -0400, Henri Yandell wrote:
> Scratch that. Brett pointed out that that may no longer be a valid question. 

Has he??

> 
> What's the current plan to fix this? Or is it a question of which
> plans to focus on?
> 
> I assume the easiest (but painful to some set of users) would be:
> 
> Rename ibiblio's 1.0 to 1.0-20040129.jar (or todays date, need to
> decide which would be best, 20040129 is the timestamp of the 1.0 on
> ibiblio currently).
> Deploy the real 1.0 to ibiblio.
> Add a README explaining the historical problem.

Well, the idea of releasing a 1.0.1 hasn't reached consensus so I'm
going to stop working on that.

As you say, the above approach may cause pain for some users. However I
would agree that the above is better than doing nothing. I can't summon
any enthusiasm for actually performing the above myself, but won't vote
against it if someone proposes formally to do this.

To modify ibiblio's setup I believe all that is necessary to do is to
log on to people.apache.org and rename/update files in directory 
  /www/www.apache.org/dist/java-repository/commons-cli
as described in section 8 of this document:
  http://jakarta.apache.org/commons/releases/release.html

I would also suggest hacking the commons-cli website directly on the
people.apache.org server, ie at:
  /www/jakarta.apache.org/commons/cli
to note that there was a problem with the 1.0 release and that people
should see the commons-cli wiki page at
  http://wiki.apache.org/jakarta-commons/CLI
for more info. And then of course the wiki page should be updated to
reflect whatever action was taken.

Note that if changes are made to a jakarta website on people.apache.org
it may take a few hours to be replicated to the actual
jakarta.apache.org server. However the changes on people.apache.org
*can* be viewed immediately via fiddling with proxy settings as
described in section 10 here:
  http://jakarta.apache.org/commons/releases/release.html


Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to