[VOTE] Release Commons Text 1.0 based on RC1

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2
Hello all,

This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).

Tag name:
   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
-v')

Tag URL:
   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
e38039a3da2244741f5d33ab1b05bdee51c53c3e

Commit ID the tag points at:
   e38039a3da2244741f5d33ab1b05bdee51c53c3e

Site:
   http://home.apache.org/~chtompki/commons-text-1.0-RC1

Distribution files (committed at revision 18567):
   https://dist.apache.org/repos/dist/dev/commons/text/

Distribution files hashes (SHA1):
   commons-text-1.0-bin.tar.gz
   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
   commons-text-1.0-bin.zip
   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
   commons-text-1.0-src.tar.gz
   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
   commons-text-1.0-src.zip
   (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)

These are the Maven artifacts and their hashes:
   commons-text-1.0-javadoc.jar
   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
   commons-text-1.0-sources.jar
   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
   commons-text-1.0-test-sources.jar
   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
   commons-text-1.0-tests.jar
   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
   commons-text-1.0.jar
   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
   commons-text-1.0.pom
   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)

KEYS file to check signatures:
   http://www.apache.org/dist/commons/KEYS

Maven artifacts:
   https://repository.apache.org/content/repositories/orgapachecommons-1239

Please select one of the following options[1]:
  [ ] +1 Release it.
  [ ] +0 Go ahead; I don't care.
  [ ] -0 There are a few minor glitches: ...
  [ ] -1 No, do not release it because ...

This vote will be open at least 72 hours, i.e. until
2017-03-09T14:00:00Z
(this is UTC time).
--------

Cheers,
-Rob

[1] http://apache.org/foundation/voting.html
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Oliver Heger-3
Hi,

build works fine with Java 1.7 and 1.8 on Windows 10, also the site
build with Java 1.8. Artifacts and site look good.

I did not find any other problems than already reported (wrong version
in release notes and one missing license header in RAT report). One
minor point: Shouldn't the 1.0 release appear under Release History?

The wrong version in the release notes is indeed annoying, but I do not
think that this is sufficient to block the release.

So +1

Oliver

Am 06.03.2017 um 14:25 schrieb Rob Tompkins:

> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
> e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>    https://repository.apache.org/content/repositories/orgapachecommons-1239
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Jörg Schaible
In reply to this post by Rob Tompkins-2
+1

Builds fine with my compiler zoo incl. Java 9.

Rob Tompkins wrote:

> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
> e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>    
https://repository.apache.org/content/repositories/orgapachecommons-1239

>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2
I’ll add my +1 (non-binding) here.

> On Mar 8, 2017, at 1:15 PM, Jörg Schaible <[hidden email]> wrote:
>
> +1
>
> Builds fine with my compiler zoo incl. Java 9.
>
> Rob Tompkins wrote:
>
>> Hello all,
>>
>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>>
>> Tag name:
>>   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>> -v')
>>
>> Tag URL:
>>   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>> e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>
>> Commit ID the tag points at:
>>   e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>
>> Site:
>>   http://home.apache.org/~chtompki/commons-text-1.0-RC1
>>
>> Distribution files (committed at revision 18567):
>>   https://dist.apache.org/repos/dist/dev/commons/text/
>>
>> Distribution files hashes (SHA1):
>>   commons-text-1.0-bin.tar.gz
>>   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>   commons-text-1.0-bin.zip
>>   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>   commons-text-1.0-src.tar.gz
>>   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>   commons-text-1.0-src.zip
>>   (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>>
>> These are the Maven artifacts and their hashes:
>>   commons-text-1.0-javadoc.jar
>>   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>   commons-text-1.0-sources.jar
>>   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>   commons-text-1.0-test-sources.jar
>>   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>   commons-text-1.0-tests.jar
>>   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>   commons-text-1.0.jar
>>   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>   commons-text-1.0.pom
>>   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>>
>> KEYS file to check signatures:
>>   http://www.apache.org/dist/commons/KEYS
>>
>> Maven artifacts:
>>
> https://repository.apache.org/content/repositories/orgapachecommons-1239
>>
>> Please select one of the following options[1]:
>>  [ ] +1 Release it.
>>  [ ] +0 Go ahead; I don't care.
>>  [ ] -0 There are a few minor glitches: ...
>>  [ ] -1 No, do not release it because ...
>>
>> This vote will be open at least 72 hours, i.e. until
>> 2017-03-09T14:00:00Z
>> (this is UTC time).
>> --------
>>
>> Cheers,
>> -Rob
>>
>> [1] http://apache.org/foundation/voting.html
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2
In reply to this post by Rob Tompkins-2
The vote can pass with the following (in order of appearance):

Bruno P. Kinoshita: +1
Oliver Heger: +1
Jörg Schaible: +1.

Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb stated.

I’m entirely willing to re-build the candidate to get a “spotless” 1.0 release. Does anyone have any thoughts regarding the value of having fewer typographical errors in a 1.0 release?

If we do go out with it, what would the process be: make sure to make the notes in the [ANNOUNCE] email?

-Rob

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1 <http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/ <https://dist.apache.org/repos/dist/dev/commons/text/>
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/commons/KEYS>
>
> Maven artifacts:
>    https://repository.apache.org/content/repositories/orgapachecommons-1239 <https://repository.apache.org/content/repositories/orgapachecommons-1239>
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html <http://apache.org/foundation/voting.html>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Bruno P. Kinoshita-3
I have never been a RM, but maybe generate new artefacts with the corrected text files, then release it and send the notes to the announce e-mail?
Users can trace the reason for the changes in your commit message and here in the vote thread.
CheersBruno
      From: Rob Tompkins <[hidden email]>
 To: [hidden email]
 Sent: Saturday, 11 March 2017 2:12 PM
 Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
   
The vote can pass with the following (in order of appearance):

Bruno P. Kinoshita: +1
Oliver Heger: +1
Jörg Schaible: +1.

Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb stated.

I’m entirely willing to re-build the candidate to get a “spotless” 1.0 release. Does anyone have any thoughts regarding the value of having fewer typographical errors in a 1.0 release?

If we do go out with it, what would the process be: make sure to make the notes in the [ANNOUNCE] email?

-Rob

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1 <http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/ <https://dist.apache.org/repos/dist/dev/commons/text/>
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/commons/KEYS>
>
> Maven artifacts:
>    https://repository.apache.org/content/repositories/orgapachecommons-1239 <https://repository.apache.org/content/repositories/orgapachecommons-1239>
>
> Please select one of the following options[1]:
>  [ ] +1 Release it.
>  [ ] +0 Go ahead; I don't care.
>  [ ] -0 There are a few minor glitches: ...
>  [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html <http://apache.org/foundation/voting.html>

   
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Matt Sicker
If you change the artefacts, that's a new release candidate. New vote, too.

On 10 March 2017 at 20:23, Bruno P. Kinoshita <
[hidden email]> wrote:

> I have never been a RM, but maybe generate new artefacts with the
> corrected text files, then release it and send the notes to the announce
> e-mail?
> Users can trace the reason for the changes in your commit message and here
> in the vote thread.
> CheersBruno
>       From: Rob Tompkins <[hidden email]>
>  To: [hidden email]
>  Sent: Saturday, 11 March 2017 2:12 PM
>  Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>
> The vote can pass with the following (in order of appearance):
>
> Bruno P. Kinoshita: +1
> Oliver Heger: +1
> Jörg Schaible: +1.
>
> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
> stated.
>
> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
> release. Does anyone have any thoughts regarding the value of having fewer
> typographical errors in a 1.0 release?
>
> If we do go out with it, what would the process be: make sure to make the
> notes in the [ANNOUNCE] email?
>
> -Rob
>
> > On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
> >
> > Hello all,
> >
> > This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
> >
> > Tag name:
> >    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> > -v')
> >
> > Tag URL:
> >    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
> e38039a3da2244741f5d33ab1b05bdee51c53c3e>
> >
> > Commit ID the tag points at:
> >    e38039a3da2244741f5d33ab1b05bdee51c53c3e
> >
> > Site:
> >    http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
> http://home.apache.org/~chtompki/commons-text-1.0-RC1>
> >
> > Distribution files (committed at revision 18567):
> >    https://dist.apache.org/repos/dist/dev/commons/text/ <
> https://dist.apache.org/repos/dist/dev/commons/text/>
> >
> > Distribution files hashes (SHA1):
> >    commons-text-1.0-bin.tar.gz
> >    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
> >    commons-text-1.0-bin.zip
> >    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
> >    commons-text-1.0-src.tar.gz
> >    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
> >    commons-text-1.0-src.zip
> >    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
> >
> > These are the Maven artifacts and their hashes:
> >    commons-text-1.0-javadoc.jar
> >    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
> >    commons-text-1.0-sources.jar
> >    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
> >    commons-text-1.0-test-sources.jar
> >    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
> >    commons-text-1.0-tests.jar
> >    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
> >    commons-text-1.0.jar
> >    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
> >    commons-text-1.0.pom
> >    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
> >
> > KEYS file to check signatures:
> >    http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/
> commons/KEYS>
> >
> > Maven artifacts:
> >    https://repository.apache.org/content/repositories/
> orgapachecommons-1239 <https://repository.apache.org/content/repositories/
> orgapachecommons-1239>
> >
> > Please select one of the following options[1]:
> >  [ ] +1 Release it.
> >  [ ] +0 Go ahead; I don't care.
> >  [ ] -0 There are a few minor glitches: ...
> >  [ ] -1 No, do not release it because ...
> >
> > This vote will be open at least 72 hours, i.e. until
> > 2017-03-09T14:00:00Z
> > (this is UTC time).
> > --------
> >
> > Cheers,
> > -Rob
> >
> > [1] http://apache.org/foundation/voting.html <
> http://apache.org/foundation/voting.html>
>
>
>



--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2

> On Mar 10, 2017, at 10:38 PM, Matt Sicker <[hidden email]> wrote:
>
> If you change the artefacts, that's a new release candidate. New vote, too.

Yes, definitely, I would need to create a new tag and go through the entire build process again. I’m just offering to do that so that the 1.0 release is cleaner. That said, we do have three +1’s so I’m definitely on the fence about making that call.

-Rob

>
> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
> [hidden email]> wrote:
>
>> I have never been a RM, but maybe generate new artefacts with the
>> corrected text files, then release it and send the notes to the announce
>> e-mail?
>> Users can trace the reason for the changes in your commit message and here
>> in the vote thread.
>> CheersBruno
>>      From: Rob Tompkins <[hidden email]>
>> To: [hidden email]
>> Sent: Saturday, 11 March 2017 2:12 PM
>> Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>>
>> The vote can pass with the following (in order of appearance):
>>
>> Bruno P. Kinoshita: +1
>> Oliver Heger: +1
>> Jörg Schaible: +1.
>>
>> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
>> stated.
>>
>> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
>> release. Does anyone have any thoughts regarding the value of having fewer
>> typographical errors in a 1.0 release?
>>
>> If we do go out with it, what would the process be: make sure to make the
>> notes in the [ANNOUNCE] email?
>>
>> -Rob
>>
>>> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>>>
>>> Hello all,
>>>
>>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>>>
>>> Tag name:
>>>   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>>> -v')
>>>
>>> Tag URL:
>>>   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
>> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
>> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>> e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>>>
>>> Commit ID the tag points at:
>>>   e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>>
>>> Site:
>>>   http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
>> http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>>>
>>> Distribution files (committed at revision 18567):
>>>   https://dist.apache.org/repos/dist/dev/commons/text/ <
>> https://dist.apache.org/repos/dist/dev/commons/text/>
>>>
>>> Distribution files hashes (SHA1):
>>>   commons-text-1.0-bin.tar.gz
>>>   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>>   commons-text-1.0-bin.zip
>>>   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>>   commons-text-1.0-src.tar.gz
>>>   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>>   commons-text-1.0-src.zip
>>>   (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>>>
>>> These are the Maven artifacts and their hashes:
>>>   commons-text-1.0-javadoc.jar
>>>   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>>   commons-text-1.0-sources.jar
>>>   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>>   commons-text-1.0-test-sources.jar
>>>   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>>   commons-text-1.0-tests.jar
>>>   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>>   commons-text-1.0.jar
>>>   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>>   commons-text-1.0.pom
>>>   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>>>
>>> KEYS file to check signatures:
>>>   http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/
>> commons/KEYS>
>>>
>>> Maven artifacts:
>>>   https://repository.apache.org/content/repositories/
>> orgapachecommons-1239 <https://repository.apache.org/content/repositories/
>> orgapachecommons-1239>
>>>
>>> Please select one of the following options[1]:
>>> [ ] +1 Release it.
>>> [ ] +0 Go ahead; I don't care.
>>> [ ] -0 There are a few minor glitches: ...
>>> [ ] -1 No, do not release it because ...
>>>
>>> This vote will be open at least 72 hours, i.e. until
>>> 2017-03-09T14:00:00Z
>>> (this is UTC time).
>>> --------
>>>
>>> Cheers,
>>> -Rob
>>>
>>> [1] http://apache.org/foundation/voting.html <
>> http://apache.org/foundation/voting.html>
>>
>>
>>
>
>
>
> --
> Matt Sicker <[hidden email]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

sebb-2-2
On 11 March 2017 at 14:41, Rob Tompkins <[hidden email]> wrote:
>
>> On Mar 10, 2017, at 10:38 PM, Matt Sicker <[hidden email]> wrote:
>>
>> If you change the artefacts, that's a new release candidate. New vote, too.
>
> Yes, definitely, I would need to create a new tag and go through the entire build process again. I’m just offering to do that so that the 1.0 release is cleaner. That said, we do have three +1’s so I’m definitely on the fence about making that call.

If the RN text error is the only problem would say it would be better
to release as is.

Just make sure that the docmentation that accompanies the release
clarifies the issue.
e.g. the Announce mail and website.

The copy of the RN which is uploaded to the ASF mirror servers could
also be fixed.
Probably best to add a prologue to say that the text was fixed after
release so people
are not confused if they notice that it disagrees with the RN in the
source/binary bundles.

> -Rob
>
>>
>> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
>> [hidden email]> wrote:
>>
>>> I have never been a RM, but maybe generate new artefacts with the
>>> corrected text files, then release it and send the notes to the announce
>>> e-mail?
>>> Users can trace the reason for the changes in your commit message and here
>>> in the vote thread.
>>> CheersBruno
>>>      From: Rob Tompkins <[hidden email]>
>>> To: [hidden email]
>>> Sent: Saturday, 11 March 2017 2:12 PM
>>> Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>>>
>>> The vote can pass with the following (in order of appearance):
>>>
>>> Bruno P. Kinoshita: +1
>>> Oliver Heger: +1
>>> Jörg Schaible: +1.
>>>
>>> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
>>> stated.
>>>
>>> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
>>> release. Does anyone have any thoughts regarding the value of having fewer
>>> typographical errors in a 1.0 release?
>>>
>>> If we do go out with it, what would the process be: make sure to make the
>>> notes in the [ANNOUNCE] email?
>>>
>>> -Rob
>>>
>>>> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>>>>
>>>> Hello all,
>>>>
>>>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>>>>
>>>> Tag name:
>>>>   commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>>>> -v')
>>>>
>>>> Tag URL:
>>>>   https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
>>> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
>>> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>>> e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>>>>
>>>> Commit ID the tag points at:
>>>>   e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>>>
>>>> Site:
>>>>   http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
>>> http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>>>>
>>>> Distribution files (committed at revision 18567):
>>>>   https://dist.apache.org/repos/dist/dev/commons/text/ <
>>> https://dist.apache.org/repos/dist/dev/commons/text/>
>>>>
>>>> Distribution files hashes (SHA1):
>>>>   commons-text-1.0-bin.tar.gz
>>>>   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>>>   commons-text-1.0-bin.zip
>>>>   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>>>   commons-text-1.0-src.tar.gz
>>>>   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>>>   commons-text-1.0-src.zip
>>>>   (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>>>>
>>>> These are the Maven artifacts and their hashes:
>>>>   commons-text-1.0-javadoc.jar
>>>>   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>>>   commons-text-1.0-sources.jar
>>>>   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>>>   commons-text-1.0-test-sources.jar
>>>>   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>>>   commons-text-1.0-tests.jar
>>>>   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>>>   commons-text-1.0.jar
>>>>   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>>>   commons-text-1.0.pom
>>>>   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>>>>
>>>> KEYS file to check signatures:
>>>>   http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/
>>> commons/KEYS>
>>>>
>>>> Maven artifacts:
>>>>   https://repository.apache.org/content/repositories/
>>> orgapachecommons-1239 <https://repository.apache.org/content/repositories/
>>> orgapachecommons-1239>
>>>>
>>>> Please select one of the following options[1]:
>>>> [ ] +1 Release it.
>>>> [ ] +0 Go ahead; I don't care.
>>>> [ ] -0 There are a few minor glitches: ...
>>>> [ ] -1 No, do not release it because ...
>>>>
>>>> This vote will be open at least 72 hours, i.e. until
>>>> 2017-03-09T14:00:00Z
>>>> (this is UTC time).
>>>> --------
>>>>
>>>> Cheers,
>>>> -Rob
>>>>
>>>> [1] http://apache.org/foundation/voting.html <
>>> http://apache.org/foundation/voting.html>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Matt Sicker <[hidden email]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins


> On Mar 11, 2017, at 10:11 AM, sebb <[hidden email]> wrote:
>
>> On 11 March 2017 at 14:41, Rob Tompkins <[hidden email]> wrote:
>>
>>> On Mar 10, 2017, at 10:38 PM, Matt Sicker <[hidden email]> wrote:
>>>
>>> If you change the artefacts, that's a new release candidate. New vote, too.
>>
>> Yes, definitely, I would need to create a new tag and go through the entire build process again. I’m just offering to do that so that the 1.0 release is cleaner. That said, we do have three +1’s so I’m definitely on the fence about making that call.
>
> If the RN text error is the only problem would say it would be better
> to release as is.
>
> Just make sure that the docmentation that accompanies the release
> clarifies the issue.
> e.g. the Announce mail and website.
>
> The copy of the RN which is uploaded to the ASF mirror servers could
> also be fixed.
> Probably best to add a prologue to say that the text was fixed after
> release so people
> are not confused if they notice that it disagrees with the RN in the
> source/binary bundles.

Okay, I'll send out the result and do the release over the next day or so.

Cheers,
-Rob

>
>> -Rob
>>
>>>
>>> On 10 March 2017 at 20:23, Bruno P. Kinoshita <
>>> [hidden email]> wrote:
>>>
>>>> I have never been a RM, but maybe generate new artefacts with the
>>>> corrected text files, then release it and send the notes to the announce
>>>> e-mail?
>>>> Users can trace the reason for the changes in your commit message and here
>>>> in the vote thread.
>>>> CheersBruno
>>>>     From: Rob Tompkins <[hidden email]>
>>>> To: [hidden email]
>>>> Sent: Saturday, 11 March 2017 2:12 PM
>>>> Subject: Re: [VOTE] Release Commons Text 1.0 based on RC1
>>>>
>>>> The vote can pass with the following (in order of appearance):
>>>>
>>>> Bruno P. Kinoshita: +1
>>>> Oliver Heger: +1
>>>> Jörg Schaible: +1.
>>>>
>>>> Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb
>>>> stated.
>>>>
>>>> I’m entirely willing to re-build the candidate to get a “spotless” 1.0
>>>> release. Does anyone have any thoughts regarding the value of having fewer
>>>> typographical errors in a 1.0 release?
>>>>
>>>> If we do go out with it, what would the process be: make sure to make the
>>>> notes in the [ANNOUNCE] email?
>>>>
>>>> -Rob
>>>>
>>>>> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>>>>>
>>>>> Tag name:
>>>>>  commons-text-1.0-RC1 (signature can be checked from git using 'git tag
>>>>> -v')
>>>>>
>>>>> Tag URL:
>>>>>  https://git-wip-us.apache.org/repos/asf?p=commons-text.git;
>>>> a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <
>>>> https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=
>>>> e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>>>>>
>>>>> Commit ID the tag points at:
>>>>>  e38039a3da2244741f5d33ab1b05bdee51c53c3e
>>>>>
>>>>> Site:
>>>>>  http://home.apache.org/~chtompki/commons-text-1.0-RC1 <
>>>> http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>>>>>
>>>>> Distribution files (committed at revision 18567):
>>>>>  https://dist.apache.org/repos/dist/dev/commons/text/ <
>>>> https://dist.apache.org/repos/dist/dev/commons/text/>
>>>>>
>>>>> Distribution files hashes (SHA1):
>>>>>  commons-text-1.0-bin.tar.gz
>>>>>  (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>>>>>  commons-text-1.0-bin.zip
>>>>>  (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>>>>>  commons-text-1.0-src.tar.gz
>>>>>  (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>>>>>  commons-text-1.0-src.zip
>>>>>  (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>>>>>
>>>>> These are the Maven artifacts and their hashes:
>>>>>  commons-text-1.0-javadoc.jar
>>>>>  (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>>>>>  commons-text-1.0-sources.jar
>>>>>  (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>>>>>  commons-text-1.0-test-sources.jar
>>>>>  (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>>>>>  commons-text-1.0-tests.jar
>>>>>  (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>>>>>  commons-text-1.0.jar
>>>>>  (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>>>>>  commons-text-1.0.pom
>>>>>  (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>>>>>
>>>>> KEYS file to check signatures:
>>>>>  http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/
>>>> commons/KEYS>
>>>>>
>>>>> Maven artifacts:
>>>>>  https://repository.apache.org/content/repositories/
>>>> orgapachecommons-1239 <https://repository.apache.org/content/repositories/
>>>> orgapachecommons-1239>
>>>>>
>>>>> Please select one of the following options[1]:
>>>>> [ ] +1 Release it.
>>>>> [ ] +0 Go ahead; I don't care.
>>>>> [ ] -0 There are a few minor glitches: ...
>>>>> [ ] -1 No, do not release it because ...
>>>>>
>>>>> This vote will be open at least 72 hours, i.e. until
>>>>> 2017-03-09T14:00:00Z
>>>>> (this is UTC time).
>>>>> --------
>>>>>
>>>>> Cheers,
>>>>> -Rob
>>>>>
>>>>> [1] http://apache.org/foundation/voting.html <
>>>> http://apache.org/foundation/voting.html>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <[hidden email]>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2
In reply to this post by Rob Tompkins-2
Here’s my +1 (non-binding).

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1 <http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/ <https://dist.apache.org/repos/dist/dev/commons/text/>
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/commons/KEYS>
>
> Maven artifacts:
>    https://repository.apache.org/content/repositories/orgapachecommons-1239 <https://repository.apache.org/content/repositories/orgapachecommons-1239>
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html <http://apache.org/foundation/voting.html>
Reply | Threaded
Open this post in threaded view
|

[RESULT][VOTE] Release Commons Text 1.0 based on RC1

Rob Tompkins-2
In reply to this post by Rob Tompkins-2
The vote passes with the following (in order of appearance):

Bruno P. Kinoshita: +1
Oliver Heger: +1
Jörg Schaible: +1, and
Rob Tompkins: +1 (non-binding)

I will proceed with publishing the release candidate. Many thanks to all of those that helped in preparing and validating this release.

Cheers,
-Rob

> On Mar 6, 2017, at 8:25 AM, Rob Tompkins <[hidden email]> wrote:
>
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
>
> Tag name:
>    commons-text-1.0-RC1 (signature can be checked from git using 'git tag
> -v')
>
> Tag URL:
>    https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e <https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e>
>
> Commit ID the tag points at:
>    e38039a3da2244741f5d33ab1b05bdee51c53c3e
>
> Site:
>    http://home.apache.org/~chtompki/commons-text-1.0-RC1 <http://home.apache.org/~chtompki/commons-text-1.0-RC1>
>
> Distribution files (committed at revision 18567):
>    https://dist.apache.org/repos/dist/dev/commons/text/ <https://dist.apache.org/repos/dist/dev/commons/text/>
>
> Distribution files hashes (SHA1):
>    commons-text-1.0-bin.tar.gz
>    (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>    commons-text-1.0-bin.zip
>    (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>    commons-text-1.0-src.tar.gz
>    (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>    commons-text-1.0-src.zip
>    (SHA1: d83eeee8bb107bcdbe58bba0525f8fd7341a2b40)
>
> These are the Maven artifacts and their hashes:
>    commons-text-1.0-javadoc.jar
>    (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>    commons-text-1.0-sources.jar
>    (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>    commons-text-1.0-test-sources.jar
>    (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>    commons-text-1.0-tests.jar
>    (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>    commons-text-1.0.jar
>    (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>    commons-text-1.0.pom
>    (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
>
> KEYS file to check signatures:
>    http://www.apache.org/dist/commons/KEYS <http://www.apache.org/dist/commons/KEYS>
>
> Maven artifacts:
>    https://repository.apache.org/content/repositories/orgapachecommons-1239 <https://repository.apache.org/content/repositories/orgapachecommons-1239>
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
> This vote will be open at least 72 hours, i.e. until
> 2017-03-09T14:00:00Z
> (this is UTC time).
> --------
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html <http://apache.org/foundation/voting.html>