+1 to both.
On 27/07/2005, at 8:37 AM, robert burrell donkin wrote:
i have included two separate votes in one email since they are closely
related.
the commons-cli-1.0 jar in the java repository
http://www.apache.org/dist/java-repository/commons-cli/jars/ is not
the
official apache commons-cli 1.0 release. this is a clear apache policy
violation and should be addressed. IMO the only way to address this
issue is to remove the jar from the repository. i will preserve the
jar
so that it can made available later.
however, users are also going to be effected by this change. this has
been discussed at length in numerous threads. this jar could be
replaced
(in the java repository) by the officially release jar. this will
ensure
that future maven builds will be accurate but may break other builds.
this action is policy neutral.
i will execute any required actions.
i propose to tally the votes no earlier than 2400 hours GMT Thursday
27th July.
i'm +1 to both proposals
- robert
--8<------------------------------------------------------------------
---
[ ] +1 Comply with ASF policy and remove the bogus jar
[ ] +0 Sounds right but too busy to investigate
[ ] -0 Sounds list a bad idea but we should comply with ASF policy
[ ] -1 Leave the jar ever though this breaks the ASF policy
----------------------------------------------------------------------
---
--8<------------------------------------------------------------------
---
[ ] +1 Upload the official commons-cli 1.0 release jar
[ ] +0 Sounds ok...
[ ] -0 Sounds bad...
[ ] -1 Do not upload the official commons-cli 1.0 release jar
----------------------------------------------------------------------
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
