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

2017-03-11 Thread Rob Tompkins 
Here’s my +1 (non-binding).

> On Mar 6, 2017, at 8:25 AM, 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> 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 
>

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

2017-03-11 Thread Rob Tompkins 


> On Mar 11, 2017, at 10:11 AM, sebb <seb...@gmail.com> wrote:
> 
>> On 11 March 2017 at 14:41, Rob Tompkins <chtom...@apache.org> wrote:
>> 
>>> On Mar 10, 2017, at 10:38 PM, Matt Sicker <boa...@gmail.com> 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 <
>>> brunodepau...@yahoo.com.br.invalid> 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 <chtom...@apache.org>
>>>> To: dev@commons.apache.org
>>>> 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 <chtom...@apache.org> 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
>>>>> 
>>>>> These are the Maven artifacts and their hashes:
>>>>>  commons-text-1.0-javadoc.jar
>>&

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

2017-03-11 Thread sebb 
On 11 March 2017 at 14:41, Rob Tompkins <chtom...@apache.org> wrote:
>
>> On Mar 10, 2017, at 10:38 PM, Matt Sicker <boa...@gmail.com> 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 <
>> brunodepau...@yahoo.com.br.invalid> 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 <chtom...@apache.org>
>>> To: dev@commons.apache.org
>>> 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 <chtom...@apache.org> 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
>>>>
>>>> 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)
>

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

2017-03-11 Thread Rob Tompkins 

> On Mar 10, 2017, at 10:38 PM, Matt Sicker <boa...@gmail.com> 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 <
> brunodepau...@yahoo.com.br.invalid> 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 <chtom...@apache.org>
>> To: dev@commons.apache.org
>> 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 <chtom...@apache.org> 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
>>> 
>>> 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 <boa...@gmail.com>


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

2017-03-11 Thread Rob Tompkins 
I’ll add my +1 (non-binding) here.

> On Mar 8, 2017, at 1:15 PM, Jörg Schaible  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: d838bb107bcdbe58bba0525f8fd7341a2b40)
>> 
>> 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: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

2017-03-10 Thread 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 <
brunodepau...@yahoo.com.br.invalid> 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 <chtom...@apache.org>
>  To: dev@commons.apache.org
>  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 <chtom...@apache.org> 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> >
> > 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 <boa...@gmail.com>

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

2017-03-10 Thread Bruno P. Kinoshita 
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 <chtom...@apache.org>
 To: dev@commons.apache.org 
 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 <chtom...@apache.org> 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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> 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>

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

2017-03-10 Thread Rob Tompkins 
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  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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> 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 
>

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

2017-03-08 Thread Jörg Schaible 
+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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> 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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

2017-03-07 Thread Oliver Heger 
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: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> 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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

2017-03-07 Thread Bruno P. Kinoshita 
[ X ] +1 Release it.

Builds OK on 

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-64-generic", arch: "amd64", family: "unix"

No major issues in the reports, signatures match, successfully generated the 
site locally.

Minor issues, non blockers I think:

* On the front page of the web site, the link to Sonar is broken

* RAT report in my computer is complaining about 
src/site/resources/release-notes/RELEASE-NOTES-1.0-beta-1.txt, but this file 
will be probably be removed during the release

* Few Tags (TODO/FIXME/etc) in the Tag List report, but I believe they are 
coming from classes migrated from [lang], so it should be fine for 1.0 release

* JIRA links for unresolved and patch needed issues are broken for me too, 
returning 50x error, but probably due to the query generated by the plugin?

* RELEASE-NOTES.txt in the dist site is mentioning the -beta release a few 
times where it should be 1.0 I think

Thanks Rob!
Bruno


- Original Message -
From: Rob Tompkins 
To: Commons Developers List 
Sent: Tuesday, 7 March 2017 2:07 AM
Subject: [VOTE] Release Commons Text 1.0 based on RC1

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: d838bb107bcdbe58bba0525f8fd7341a2b40)

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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org