You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Simone Tripodi <si...@gmail.com> on 2010/09/11 12:43:16 UTC
[VOTE] Release Digester 2.1 based on RC1
Hi all guys,
on behalf of the Digester committers I'd like to invite you to vote
the 2.1 release of the commons-digester.
Tag:
https://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_1_RC1/
Release notes:
http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
Site:
http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
Binaries:
http://people.apache.org/builds/commons/digester/2.1/RC1/staged/commons-digester/commons-digester/2.1-RC1/
Votes, please. This vote will close in 72 hours (14 Sept, 11:00am GMT).
Thanks in advance.
Simo
---------------------------------------------------------
[ ] +1 release it
[ ] +0 OK, but...
[ ] -0 Would really like to see...
[ ] -1 no, do not release it because...
---------------------------------------------------------
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Simone Tripodi <si...@gmail.com>.
Hi,
just to close this thread since the Sebastian's -1 (with reasons!)
blocked the RC1.
I'll push the RC2 soon.
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 12, 2010 at 9:49 PM, Simone Tripodi
<si...@gmail.com> wrote:
> Hi Rahul
> Thanks a lot for the suggestions, very appreciated, I applied them :)
> All the best,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sun, Sep 12, 2010 at 8:26 PM, Rahul Akolkar <ra...@gmail.com> wrote:
>> On Sat, Sep 11, 2010 at 6:43 AM, Simone Tripodi
>> <si...@gmail.com> wrote:
>> <snip/>
>>>
>>> Release notes:
>>>
>>> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>>>
>> <snap/>
>>
>> Since readability is important for release notes, I'll nitpick:
>> * Line width is inconsistent
>> * s/meta data-based/meta-data based/
>> * s/run-time/runtime/
>> * s/This is the first Digester release oriented to be built by Apache
>> Maven only./This is the first Digester release that provides an Apache
>> Maven 2 build only. The Apache Maven 1 and Apache Ant builds have been
>> removed./
>>
>>
>>> Site:
>>>
>>> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>>>
>> <snap/>
>>
>> We should advertise the new annotations stuff more. I suggest:
>> * Adding a fourth bullet (or better, a separate para) mentioning
>> the annotations work in the "The Digester Component" section on top of
>> the home page
>> * Mention in a sentence that 2.1 adds annotations support in
>> "Releases" section of home page
>>
>> The Javadoc (SVN latest) link may need a leading slash in the site.xml.
>>
>> -Rahul
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Simone Tripodi <si...@gmail.com>.
Hi Rahul
Thanks a lot for the suggestions, very appreciated, I applied them :)
All the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 12, 2010 at 8:26 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sat, Sep 11, 2010 at 6:43 AM, Simone Tripodi
> <si...@gmail.com> wrote:
> <snip/>
>>
>> Release notes:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>>
> <snap/>
>
> Since readability is important for release notes, I'll nitpick:
> * Line width is inconsistent
> * s/meta data-based/meta-data based/
> * s/run-time/runtime/
> * s/This is the first Digester release oriented to be built by Apache
> Maven only./This is the first Digester release that provides an Apache
> Maven 2 build only. The Apache Maven 1 and Apache Ant builds have been
> removed./
>
>
>> Site:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>>
> <snap/>
>
> We should advertise the new annotations stuff more. I suggest:
> * Adding a fourth bullet (or better, a separate para) mentioning
> the annotations work in the "The Digester Component" section on top of
> the home page
> * Mention in a sentence that 2.1 adds annotations support in
> "Releases" section of home page
>
> The Javadoc (SVN latest) link may need a leading slash in the site.xml.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sat, Sep 11, 2010 at 6:43 AM, Simone Tripodi
<si...@gmail.com> wrote:
<snip/>
>
> Release notes:
>
> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>
<snap/>
Since readability is important for release notes, I'll nitpick:
* Line width is inconsistent
* s/meta data-based/meta-data based/
* s/run-time/runtime/
* s/This is the first Digester release oriented to be built by Apache
Maven only./This is the first Digester release that provides an Apache
Maven 2 build only. The Apache Maven 1 and Apache Ant builds have been
removed./
> Site:
>
> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>
<snap/>
We should advertise the new annotations stuff more. I suggest:
* Adding a fourth bullet (or better, a separate para) mentioning
the annotations work in the "The Digester Component" section on top of
the home page
* Mention in a sentence that 2.1 adds annotations support in
"Releases" section of home page
The Javadoc (SVN latest) link may need a leading slash in the site.xml.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sat, Sep 11, 2010 at 11:20 AM, sebb <se...@gmail.com> wrote:
> On 11 September 2010 11:43, Simone Tripodi <si...@gmail.com> wrote:
>> Hi all guys,
>> on behalf of the Digester committers I'd like to invite you to vote
>> the 2.1 release of the commons-digester.
>>
>> Tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_1_RC1/
>>
>> Release notes:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>>
>> Site:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>
> Fixed a minor typo - missing "(" - not a blocker.
>
>> Binaries:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/staged/commons-digester/commons-digester/2.1-RC1/
>
> SIgniing key is listed in public databases, but does not appear to be in:
>
> https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS
>
> This needs to be updated as per the instructions contained in it.
>
> The <scm> entries in pom.xml refer to /tags/DIGESTER_2_1_RC1.
> However, if the vote succeeds, the tag should be renamed to remove the
> _RC1 suffix - and the scm entries will then be invalid.
>
<snip/>
For this, I leave the successful RC tag and the final tag around. IMO
thats good enough.
> There are similar problems with the Specification-Version: and
> Implementation-Version: in the MANIFEST files.
>
> Also, the directory names include RC1.
>
> Given that the RC version is defined here:
>
> <commons.rc.version>RC1</commons.rc.version>
>
> perhaps
>
> <version>2.1-RC1</version>
>
> should be
>
> <version>2.1</version>
>
> Not sure if this works with the Maven release plugin.
>
<snap/>
Here is what I do with the release plugin (using soon to come RC2 as example):
* When prompted for the version, use 2.1
* When prompted for the tag, use DIGESTER_2_1_RC2
Voting on the exact bits leads to the first bullet, that this isn't
the actual release until it passes muster leads to the second.
<commons.rc.version> is updated manually before each RC.
-Rahul
> The .asc.md5 and .asc.sha1 files ought to be deleted before files are
> released to Maven Central. Just delete them from the staging area.
>
> Sorry, but IMO this warrants -1 because of the RCn version problems.
>
>> Votes, please. This vote will close in 72 hours (14 Sept, 11:00am GMT).
>>
>> Thanks in advance.
>> Simo
>>
>> ---------------------------------------------------------
>>
>> [ ] +1 release it
>> [ ] +0 OK, but...
>> [ ] -0 Would really like to see...
>> [ ] -1 no, do not release it because...
>>
>> ---------------------------------------------------------
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Simone Tripodi <si...@gmail.com>.
excellent, I thought the same and agree with this!!!
all the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 12, 2010 at 5:37 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sun, Sep 12, 2010 at 11:33 AM, Simone Tripodi
> <si...@gmail.com> wrote:
>> Thanks a lot for the clarifications Rahul!!! :)
> <snip/>
>
> I'd also add its best to wait a few days (3+) before rolling the next
> RC to allow time for any additional feedback.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sun, Sep 12, 2010 at 11:33 AM, Simone Tripodi
<si...@gmail.com> wrote:
> Thanks a lot for the clarifications Rahul!!! :)
<snip/>
I'd also add its best to wait a few days (3+) before rolling the next
RC to allow time for any additional feedback.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Simone Tripodi <si...@gmail.com>.
Thanks a lot for the clarifications Rahul!!! :)
Have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sun, Sep 12, 2010 at 5:24 PM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Sun, Sep 12, 2010 at 7:20 AM, sebb <se...@gmail.com> wrote:
>> On 12 September 2010 08:09, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi Seb,
>>> thanks for the feedbacks, my fault: I misunderstood the tag creation,
>>> I manually forced the -RCn postfix :( So now 2 questions to increase
>>> my knowledge:
>>>
>>> 1) shall the /DIGESTER_2_1_RC1/ tag be deleted? I'd say 'yes' but
>>> waiting for your confirmation.
>>
>> If it no longer has any use, it can be deleted.
>>
>> In this case the tag was used for a vote, so I'd leave deletion until
>> after the release process completes.
>> The tag may be useful for comparison purposes.
>>
> <snip/>
>
> Yes, there is no rush to delete. I tend to leave all RC tags in SVN
> (as you can tell by looking at the tags directory).
>
>
>>> 2) if an RCn fails, when releasing an RCn+1, the tag dir has o be
>>> deleted and recreated, right?
>>
>> Ideally tags are a fixed version and are never recreated.
>>
> <snap/>
>
> Indeed.
>
>
>> So I would create the new tag, and later delete the old tag.
>>
> <snip/>
>
> Caveat being retain the tag for the successful RC since you're using
> the release plugin (for <scm> bits).
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Rahul Akolkar <ra...@gmail.com>.
On Sun, Sep 12, 2010 at 7:20 AM, sebb <se...@gmail.com> wrote:
> On 12 September 2010 08:09, Simone Tripodi <si...@gmail.com> wrote:
>> Hi Seb,
>> thanks for the feedbacks, my fault: I misunderstood the tag creation,
>> I manually forced the -RCn postfix :( So now 2 questions to increase
>> my knowledge:
>>
>> 1) shall the /DIGESTER_2_1_RC1/ tag be deleted? I'd say 'yes' but
>> waiting for your confirmation.
>
> If it no longer has any use, it can be deleted.
>
> In this case the tag was used for a vote, so I'd leave deletion until
> after the release process completes.
> The tag may be useful for comparison purposes.
>
<snip/>
Yes, there is no rush to delete. I tend to leave all RC tags in SVN
(as you can tell by looking at the tags directory).
>> 2) if an RCn fails, when releasing an RCn+1, the tag dir has o be
>> deleted and recreated, right?
>
> Ideally tags are a fixed version and are never recreated.
>
<snap/>
Indeed.
> So I would create the new tag, and later delete the old tag.
>
<snip/>
Caveat being retain the tag for the successful RC since you're using
the release plugin (for <scm> bits).
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by sebb <se...@gmail.com>.
On 12 September 2010 08:09, Simone Tripodi <si...@gmail.com> wrote:
> Hi Seb,
> thanks for the feedbacks, my fault: I misunderstood the tag creation,
> I manually forced the -RCn postfix :( So now 2 questions to increase
> my knowledge:
>
> 1) shall the /DIGESTER_2_1_RC1/ tag be deleted? I'd say 'yes' but
> waiting for your confirmation.
If it no longer has any use, it can be deleted.
In this case the tag was used for a vote, so I'd leave deletion until
after the release process completes.
The tag may be useful for comparison purposes.
> 2) if an RCn fails, when releasing an RCn+1, the tag dir has o be
> deleted and recreated, right?
Ideally tags are a fixed version and are never recreated.
So I would create the new tag, and later delete the old tag.
>
> Many thanks in advance, have a nice Sunday,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Sat, Sep 11, 2010 at 5:20 PM, sebb <se...@gmail.com> wrote:
>> On 11 September 2010 11:43, Simone Tripodi <si...@gmail.com> wrote:
>>> Hi all guys,
>>> on behalf of the Digester committers I'd like to invite you to vote
>>> the 2.1 release of the commons-digester.
>>>
>>> Tag:
>>>
>>> https://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_1_RC1/
>>>
>>> Release notes:
>>>
>>> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>>>
>>> Site:
>>>
>>> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>>
>> Fixed a minor typo - missing "(" - not a blocker.
>>
>>> Binaries:
>>>
>>> http://people.apache.org/builds/commons/digester/2.1/RC1/staged/commons-digester/commons-digester/2.1-RC1/
>>
>> SIgniing key is listed in public databases, but does not appear to be in:
>>
>> https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS
>>
>> This needs to be updated as per the instructions contained in it.
>>
>> The <scm> entries in pom.xml refer to /tags/DIGESTER_2_1_RC1.
>> However, if the vote succeeds, the tag should be renamed to remove the
>> _RC1 suffix - and the scm entries will then be invalid.
>>
>> There are similar problems with the Specification-Version: and
>> Implementation-Version: in the MANIFEST files.
>>
>> Also, the directory names include RC1.
>>
>> Given that the RC version is defined here:
>>
>> <commons.rc.version>RC1</commons.rc.version>
>>
>> perhaps
>>
>> <version>2.1-RC1</version>
>>
>> should be
>>
>> <version>2.1</version>
>>
>> Not sure if this works with the Maven release plugin.
>>
>> The .asc.md5 and .asc.sha1 files ought to be deleted before files are
>> released to Maven Central. Just delete them from the staging area.
>>
>> Sorry, but IMO this warrants -1 because of the RCn version problems.
>>
>>> Votes, please. This vote will close in 72 hours (14 Sept, 11:00am GMT).
>>>
>>> Thanks in advance.
>>> Simo
>>>
>>> ---------------------------------------------------------
>>>
>>> [ ] +1 release it
>>> [ ] +0 OK, but...
>>> [ ] -0 Would really like to see...
>>> [ ] -1 no, do not release it because...
>>>
>>> ---------------------------------------------------------
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by Simone Tripodi <si...@gmail.com>.
Hi Seb,
thanks for the feedbacks, my fault: I misunderstood the tag creation,
I manually forced the -RCn postfix :( So now 2 questions to increase
my knowledge:
1) shall the /DIGESTER_2_1_RC1/ tag be deleted? I'd say 'yes' but
waiting for your confirmation.
2) if an RCn fails, when releasing an RCn+1, the tag dir has o be
deleted and recreated, right?
Many thanks in advance, have a nice Sunday,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Sep 11, 2010 at 5:20 PM, sebb <se...@gmail.com> wrote:
> On 11 September 2010 11:43, Simone Tripodi <si...@gmail.com> wrote:
>> Hi all guys,
>> on behalf of the Digester committers I'd like to invite you to vote
>> the 2.1 release of the commons-digester.
>>
>> Tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_1_RC1/
>>
>> Release notes:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>>
>> Site:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
>
> Fixed a minor typo - missing "(" - not a blocker.
>
>> Binaries:
>>
>> http://people.apache.org/builds/commons/digester/2.1/RC1/staged/commons-digester/commons-digester/2.1-RC1/
>
> SIgniing key is listed in public databases, but does not appear to be in:
>
> https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS
>
> This needs to be updated as per the instructions contained in it.
>
> The <scm> entries in pom.xml refer to /tags/DIGESTER_2_1_RC1.
> However, if the vote succeeds, the tag should be renamed to remove the
> _RC1 suffix - and the scm entries will then be invalid.
>
> There are similar problems with the Specification-Version: and
> Implementation-Version: in the MANIFEST files.
>
> Also, the directory names include RC1.
>
> Given that the RC version is defined here:
>
> <commons.rc.version>RC1</commons.rc.version>
>
> perhaps
>
> <version>2.1-RC1</version>
>
> should be
>
> <version>2.1</version>
>
> Not sure if this works with the Maven release plugin.
>
> The .asc.md5 and .asc.sha1 files ought to be deleted before files are
> released to Maven Central. Just delete them from the staging area.
>
> Sorry, but IMO this warrants -1 because of the RCn version problems.
>
>> Votes, please. This vote will close in 72 hours (14 Sept, 11:00am GMT).
>>
>> Thanks in advance.
>> Simo
>>
>> ---------------------------------------------------------
>>
>> [ ] +1 release it
>> [ ] +0 OK, but...
>> [ ] -0 Would really like to see...
>> [ ] -1 no, do not release it because...
>>
>> ---------------------------------------------------------
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Digester 2.1 based on RC1
Posted by sebb <se...@gmail.com>.
On 11 September 2010 11:43, Simone Tripodi <si...@gmail.com> wrote:
> Hi all guys,
> on behalf of the Digester committers I'd like to invite you to vote
> the 2.1 release of the commons-digester.
>
> Tag:
>
> https://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_1_RC1/
>
> Release notes:
>
> http://people.apache.org/builds/commons/digester/2.1/RC1/RELEASE-NOTES.txt
>
> Site:
>
> http://people.apache.org/builds/commons/digester/2.1/RC1/site/index.html
Fixed a minor typo - missing "(" - not a blocker.
> Binaries:
>
> http://people.apache.org/builds/commons/digester/2.1/RC1/staged/commons-digester/commons-digester/2.1-RC1/
SIgniing key is listed in public databases, but does not appear to be in:
https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS
This needs to be updated as per the instructions contained in it.
The <scm> entries in pom.xml refer to /tags/DIGESTER_2_1_RC1.
However, if the vote succeeds, the tag should be renamed to remove the
_RC1 suffix - and the scm entries will then be invalid.
There are similar problems with the Specification-Version: and
Implementation-Version: in the MANIFEST files.
Also, the directory names include RC1.
Given that the RC version is defined here:
<commons.rc.version>RC1</commons.rc.version>
perhaps
<version>2.1-RC1</version>
should be
<version>2.1</version>
Not sure if this works with the Maven release plugin.
The .asc.md5 and .asc.sha1 files ought to be deleted before files are
released to Maven Central. Just delete them from the staging area.
Sorry, but IMO this warrants -1 because of the RCn version problems.
> Votes, please. This vote will close in 72 hours (14 Sept, 11:00am GMT).
>
> Thanks in advance.
> Simo
>
> ---------------------------------------------------------
>
> [ ] +1 release it
> [ ] +0 OK, but...
> [ ] -0 Would really like to see...
> [ ] -1 no, do not release it because...
>
> ---------------------------------------------------------
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org