[GitHub] commons-dbutils issue #3: Fixes a thread safety problem introduced by DBUTIL...

2018-01-16 Thread objectboy2016 
Github user objectboy2016 commented on the issue:

https://github.com/apache/commons-dbutils/pull/3
  
**Why not design a named parameter** 
such as: 
 string sql="select * from user where name=:name";
 ...
 runquery.addParameter("name","paul");

So simple and straightforward
No problem with the number, but the parameters of many will be a disaster

such as:
insert into a (a, b, c, d, f, g, i, e, g, k) values (?,?,?,?,?,?,?,?,?)

My eyes have been spent


---

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

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Stian Soiland-Reyes 
+1 (Binding)

(While I might disagree in principle about removing source .tar.gz and
.zip from Maven repo, I say let's get the plugin released and find
more bugs later! :) )

Checked:

+1 gpg signatures
+1 sha1, md5
+1 source zip vs tar.gz
+1 binary zip vs tar.gz
+1 source vs git (for some reason git has duplicate LICENSE as well as
LICENSE.txt)
+1 mvn apache-rat:check
+1 no binaries (except test archives)
+1 LICENSE, NOTICE
+0 README refers to
https://commons.apache.org/proper/commons-commons-release-plugin/javadocs/api-release
which is 404 Not Found (site.zip has apidocs/)
+1 RELEASE-NOTES
+1 mvn clean install
+0 mvn repository kind of matches src? *)

*) I was unable to verify that
https://repository.apache.org/content/repositories/orgapachecommons-1302
contained artifacts from building this RC as the Maven repo do not
include the source zip/tar.gz (see principle above)




Tested with:

Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family: "unix"

On 11 January 2018 at 02:50, Rob Tompkins  wrote:
> Hello all,
>
> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from RC1).
>
> Tag name:
>commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>
> Commit ID the tag points at:
>2f48a0ebd07318419b4d92a7e7b594f4fca47428
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
>
> Distribution files (committed at revision 24125):
>https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>
> Distribution files hashes (SHA1):
>   commons-release-plugin-1.0-bin.tar.gz
>   (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>   commons-release-plugin-1.0-bin.zip
>   (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>   commons-release-plugin-1.0-src.tar.gz
>   (SHA1: e48b67b70b154b7dc69914752814512225024504)
>   commons-release-plugin-1.0-src.zip
>   (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>
> These are the Maven artifacts and their hashes:
>   commons-release-plugin-1.0-javadoc.jar
>   (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>   commons-release-plugin-1.0-sources.jar
>   (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>   commons-release-plugin-1.0-test-sources.jar
>   (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>   commons-release-plugin-1.0-tests.jar
>   (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>   commons-release-plugin-1.0.jar
>   (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>   commons-release-plugin-1.0.pom
>   (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1302
>
> 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
> 2018-01-14T03: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
>



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

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

Re: [Statistics] Language level

2018-01-16 Thread Sergio Fernández 
I think the de facto rule for all new components should be the current JDK
LTS.

So +1 for Java 8.

On Jan 15, 2018 15:01, "Gilles"  wrote:

> Hi
>
> Which should we target for that component?
> IOW, has someone a case for less than Java 8?
>
> Gilles
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [Statistics] Distributions

2018-01-16 Thread Bill Igoe 
Giles,

Seems reasonable.

Thinking aloud.  'Math' is of course a broad subject and your goal of a
solid all encompassing package is admirable.
Managing a lot of jars or packages is a pain for the none java expert. In
thinking on the way python, R and other packages
solves the 'issue' is by automatically  downloading dependencies.

So might we create a MathManager.java class concept to aid in development.
Again thinking aloud.  Say we begin with a simple MathManager class. Our
code query's MathManger ,which is a wrapper for a sophisticated java
classloader
 that
automatically querys a users disk for the required jars, if not found the
MathManager querys a repository server for the the required jar and then
downloads, saves  and loads the required  byte code.  Thus the concept of
'Math' may include many developers from different fields. MathManager would
check for updates upon any class request and keep a central repository on
the users disk in synch with all future development.  The reduction in
speed would be negligible as the classloader is in use in everyday byte
code generation.

Sound busy and complicated at first but you might get the exponential
explosion of some very interesting code across the entire math discipline.
Python is highly successful in using this concept.

Bill




On Mon, Jan 15, 2018 at 5:10 AM, Gilles 
wrote:

> Hi.
>
> Please have a look at the issue created on JIRA:
>   https://issues.apache.org/jira/projects/STATISTICS/issues/STATISTICS-2
> and give your opinion.
>
> Thanks,
> Gilles
>
> On Sat, 13 Jan 2018 13:38:26 +0100, Gilles wrote:
>
>> [...]
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [Statistics] Distributions

2018-01-16 Thread Eric Barnhill 
On Tue, Jan 16, 2018 at 3:29 PM, Bill Igoe  wrote:

>
> Thinking aloud.  'Math' is of course a broad subject and your goal of a
> solid all encompassing package is admirable.
>

I am not sure that is the goal of the projects here actually. Commons is
more about small re-usable components that emerge in a wide range of
applications. I think our goal is not to rival SciPy, or be a full service
scientific library like ImgLib2.


> Managing a lot of jars or packages is a pain for the none java expert. In
> thinking on the way python, R and other packages
> solves the 'issue' is by automatically  downloading dependencies.
>

Do you have much familiarity with Maven? Commons is built with maven and I
use it in all my projects as well. If you ask me maven is a very slick
package manager, easily to rival anything in Python or R, and one reason I
enjoy continuing to work in Java.

Eric

Re: [Statistics] Distributions

2018-01-16 Thread Bill Igoe 
Just read the Maven description bingo!!!

On Tue, Jan 16, 2018 at 8:02 AM, Eric Barnhill 
wrote:

> On Tue, Jan 16, 2018 at 3:29 PM, Bill Igoe  wrote:
>
> >
> > Thinking aloud.  'Math' is of course a broad subject and your goal of a
> > solid all encompassing package is admirable.
> >
>
> I am not sure that is the goal of the projects here actually. Commons is
> more about small re-usable components that emerge in a wide range of
> applications. I think our goal is not to rival SciPy, or be a full service
> scientific library like ImgLib2.
>
>
> > Managing a lot of jars or packages is a pain for the none java expert. In
> > thinking on the way python, R and other packages
> > solves the 'issue' is by automatically  downloading dependencies.
> >
>
> Do you have much familiarity with Maven? Commons is built with maven and I
> use it in all my projects as well. If you ask me maven is a very slick
> package manager, easily to rival anything in Python or R, and one reason I
> enjoy continuing to work in Java.
>
> Eric
>

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Rob Tompkins 
Curious if anyone else wants to weigh in?

> On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes  wrote:
> 
> +1 (Binding)
> 
> (While I might disagree in principle about removing source .tar.gz and
> .zip from Maven repo, I say let's get the plugin released and find
> more bugs later! :) )
> 

This *should* be a configurable option. I don’t think though that it is in this 
version of the plugin. Personally, I want the plugin to accommodate any process 
that the project may use. So as the process changes one direction or another, 
so should the plugin. 

> Checked:
> 
> +1 gpg signatures
> +1 sha1, md5
> +1 source zip vs tar.gz
> +1 binary zip vs tar.gz
> +1 source vs git (for some reason git has duplicate LICENSE as well as
> LICENSE.txt)
> +1 mvn apache-rat:check
> +1 no binaries (except test archives)
> +1 LICENSE, NOTICE
> +0 README refers to
> https://commons.apache.org/proper/commons-commons-release-plugin/javadocs/api-release
> which is 404 Not Found (site.zip has apidocs/)
> +1 RELEASE-NOTES
> +1 mvn clean install
> +0 mvn repository kind of matches src? *)
> 
> *) I was unable to verify that
> https://repository.apache.org/content/repositories/orgapachecommons-1302
> contained artifacts from building this RC as the Maven repo do not
> include the source zip/tar.gz (see principle above)
> 
> 
> 
> 
> Tested with:
> 
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family: "unix"
> 
>> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
>> Hello all,
>> 
>> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from RC1).
>> 
>> Tag name:
>>   commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>> 
>> Commit ID the tag points at:
>>   2f48a0ebd07318419b4d92a7e7b594f4fca47428
>> 
>> Site:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
>> 
>> Distribution files (committed at revision 24125):
>>   https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>> 
>> Distribution files hashes (SHA1):
>>  commons-release-plugin-1.0-bin.tar.gz
>>  (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>>  commons-release-plugin-1.0-bin.zip
>>  (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>>  commons-release-plugin-1.0-src.tar.gz
>>  (SHA1: e48b67b70b154b7dc69914752814512225024504)
>>  commons-release-plugin-1.0-src.zip
>>  (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>> 
>> These are the Maven artifacts and their hashes:
>>  commons-release-plugin-1.0-javadoc.jar
>>  (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>>  commons-release-plugin-1.0-sources.jar
>>  (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>>  commons-release-plugin-1.0-test-sources.jar
>>  (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>>  commons-release-plugin-1.0-tests.jar
>>  (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>>  commons-release-plugin-1.0.jar
>>  (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>>  commons-release-plugin-1.0.pom
>>  (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>> 
>> KEYS file to check signatures:
>>   http://www.apache.org/dist/commons/KEYS
>> 
>> Maven artifacts:
>>   https://repository.apache.org/content/repositories/orgapachecommons-1302
>> 
>> 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
>> 2018-01-14T03: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
>> 
> 
> 
> 
> -- 
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
> 
> -
> 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: Fwd: [jira] [Created] (COMDEV-248) add /dist/ health issues

2018-01-16 Thread Sergio Fernández 
Hi Gilles,

On Thu, Jan 11, 2018 at 3:41 AM, Gilles 
wrote:

> On Thu, 11 Jan 2018 12:35:35 +0100, Sergio Fernández wrote:
>
>> From ComDev, just discovered checker.a.o, and got into the following
>> report
>> with problems:
>>
>> https://checker.apache.org/projs/commons.html
>>
>> What do we usually do with such problems on dormant components?
>>
>
> IIUC, this
>   http://www.apache.org/legal/release-policy.html#when-to-archive
> says that they must be removed from the "dist" area.
>

Then I'll do so later from home, if I have enough karma.

Cheers,

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Otto Fowler 
Do you have a page with the verification steps and requirements?


On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com) wrote:

Curious if anyone else wants to weigh in?

> On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
wrote:
>
> +1 (Binding)
>
> (While I might disagree in principle about removing source .tar.gz and
> .zip from Maven repo, I say let's get the plugin released and find
> more bugs later! :) )
>

This *should* be a configurable option. I don’t think though that it is in
this version of the plugin. Personally, I want the plugin to accommodate
any process that the project may use. So as the process changes one
direction or another, so should the plugin.

> Checked:
>
> +1 gpg signatures
> +1 sha1, md5
> +1 source zip vs tar.gz
> +1 binary zip vs tar.gz
> +1 source vs git (for some reason git has duplicate LICENSE as well as
> LICENSE.txt)
> +1 mvn apache-rat:check
> +1 no binaries (except test archives)
> +1 LICENSE, NOTICE
> +0 README refers to
>
https://commons.apache.org/proper/commons-commons-release-plugin/javadocs/api-release
> which is 404 Not Found (site.zip has apidocs/)
> +1 RELEASE-NOTES
> +1 mvn clean install
> +0 mvn repository kind of matches src? *)
>
> *) I was unable to verify that
> https://repository.apache.org/content/repositories/orgapachecommons-1302
> contained artifacts from building this RC as the Maven repo do not
> include the source zip/tar.gz (see principle above)
>
>
>
>
> Tested with:
>
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
"unix"
>
>> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
>> Hello all,
>>
>> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
RC1).
>>
>> Tag name:
>> commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>>
>> Commit ID the tag points at:
>> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
>>
>> Site:
>>
https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
>>
>> Distribution files (committed at revision 24125):
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>>
>> Distribution files hashes (SHA1):
>> commons-release-plugin-1.0-bin.tar.gz
>> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>> commons-release-plugin-1.0-bin.zip
>> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>> commons-release-plugin-1.0-src.tar.gz
>> (SHA1: e48b67b70b154b7dc69914752814512225024504)
>> commons-release-plugin-1.0-src.zip
>> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>>
>> These are the Maven artifacts and their hashes:
>> commons-release-plugin-1.0-javadoc.jar
>> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>> commons-release-plugin-1.0-sources.jar
>> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>> commons-release-plugin-1.0-test-sources.jar
>> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>> commons-release-plugin-1.0-tests.jar
>> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>> commons-release-plugin-1.0.jar
>> (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>> commons-release-plugin-1.0.pom
>> (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>>
>> KEYS file to check signatures:
>> http://www.apache.org/dist/commons/KEYS
>>
>> Maven artifacts:
>> https://repository.apache.org/content/repositories/orgapachecommons-1302
>>
>> 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
>> 2018-01-14T03: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
>>
>
>
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>
> -
> 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: [All] Source compatibility policy

2018-01-16 Thread Pascal Schumacher 

Am 16.01.2018 um 00:06 schrieb Gary Gregory:

For me, breaking source compatibility should be limited to what can be
adjusted to in my sources very easily. I would also consider whether the
breaks are for a cosmetic reasons for an actual bug fix. I would probably
pass on cosmetic breaks within minor releases.

In this case, an exception declared unnecessarily can make client code more
cumbersome, but not always, if other parts of the code happen to throw the
same exception.

More important is binary compatibility, which we should not break within
minor releases. What happens in this case to BC?


"Changes to the |throws| clause of methods or constructors do not break 
compatibility with pre-existing binaries; these clauses are checked only 
at compile time."


Source: 
https://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html#jls-13.4.21


Clirr does not report any errors or warnings.

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Gary Gregory 
I think you have enough VOTEs from the PMC ATM. Tally?

Gary

On Tue, Jan 16, 2018 at 10:17 AM, Otto Fowler 
wrote:

> Do you have a page with the verification steps and requirements?
>
>
> On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com) wrote:
>
> Curious if anyone else wants to weigh in?
>
> > On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
> wrote:
> >
> > +1 (Binding)
> >
> > (While I might disagree in principle about removing source .tar.gz and
> > .zip from Maven repo, I say let's get the plugin released and find
> > more bugs later! :) )
> >
>
> This *should* be a configurable option. I don’t think though that it is in
> this version of the plugin. Personally, I want the plugin to accommodate
> any process that the project may use. So as the process changes one
> direction or another, so should the plugin.
>
> > Checked:
> >
> > +1 gpg signatures
> > +1 sha1, md5
> > +1 source zip vs tar.gz
> > +1 binary zip vs tar.gz
> > +1 source vs git (for some reason git has duplicate LICENSE as well as
> > LICENSE.txt)
> > +1 mvn apache-rat:check
> > +1 no binaries (except test archives)
> > +1 LICENSE, NOTICE
> > +0 README refers to
> >
> https://commons.apache.org/proper/commons-commons-
> release-plugin/javadocs/api-release
> > which is 404 Not Found (site.zip has apidocs/)
> > +1 RELEASE-NOTES
> > +1 mvn clean install
> > +0 mvn repository kind of matches src? *)
> >
> > *) I was unable to verify that
> > https://repository.apache.org/content/repositories/orgapachecommons-1302
> > contained artifacts from building this RC as the Maven repo do not
> > include the source zip/tar.gz (see principle above)
> >
> >
> >
> >
> > Tested with:
> >
> > Apache Maven 3.3.9
> > Maven home: /usr/share/maven
> > Java version: 1.8.0_151, vendor: Oracle Corporation
> > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> > Default locale: en_GB, platform encoding: UTF-8
> > OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
> "unix"
> >
> >> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
> >> Hello all,
> >>
> >> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
> RC1).
> >>
> >> Tag name:
> >> commons-release-plugin-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-release-
> plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
> >>
> >> Commit ID the tag points at:
> >> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
> >>
> >> Site:
> >>
> https://dist.apache.org/repos/dist/dev/commons/commons-
> release-plugin/site.zip
> >>
> >> Distribution files (committed at revision 24125):
> >> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
> >>
> >> Distribution files hashes (SHA1):
> >> commons-release-plugin-1.0-bin.tar.gz
> >> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
> >> commons-release-plugin-1.0-bin.zip
> >> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
> >> commons-release-plugin-1.0-src.tar.gz
> >> (SHA1: e48b67b70b154b7dc69914752814512225024504)
> >> commons-release-plugin-1.0-src.zip
> >> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
> >>
> >> These are the Maven artifacts and their hashes:
> >> commons-release-plugin-1.0-javadoc.jar
> >> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
> >> commons-release-plugin-1.0-sources.jar
> >> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
> >> commons-release-plugin-1.0-test-sources.jar
> >> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
> >> commons-release-plugin-1.0-tests.jar
> >> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
> >> commons-release-plugin-1.0.jar
> >> (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
> >> commons-release-plugin-1.0.pom
> >> (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
> >>
> >> KEYS file to check signatures:
> >> http://www.apache.org/dist/commons/KEYS
> >>
> >> Maven artifacts:
> >> https://repository.apache.org/content/repositories/
> orgapachecommons-1302
> >>
> >> 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
> >> 2018-01-14T03: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
> >>
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > http://orcid.org/-0001-9842-9718
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Rob Tompkins 
I’ll do the tally tonight (UTC-5). Should the announce only go to the dev list?

> On Jan 16, 2018, at 2:40 PM, Gary Gregory  wrote:
> 
> I think you have enough VOTEs from the PMC ATM. Tally?
> 
> Gary
> 
>> On Tue, Jan 16, 2018 at 10:17 AM, Otto Fowler  
>> wrote:
>> Do you have a page with the verification steps and requirements?
>> 
>> 
>> On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com) wrote:
>> 
>> Curious if anyone else wants to weigh in?
>> 
>> > On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
>> wrote:
>> >
>> > +1 (Binding)
>> >
>> > (While I might disagree in principle about removing source .tar.gz and
>> > .zip from Maven repo, I say let's get the plugin released and find
>> > more bugs later! :) )
>> >
>> 
>> This *should* be a configurable option. I don’t think though that it is in
>> this version of the plugin. Personally, I want the plugin to accommodate
>> any process that the project may use. So as the process changes one
>> direction or another, so should the plugin.
>> 
>> > Checked:
>> >
>> > +1 gpg signatures
>> > +1 sha1, md5
>> > +1 source zip vs tar.gz
>> > +1 binary zip vs tar.gz
>> > +1 source vs git (for some reason git has duplicate LICENSE as well as
>> > LICENSE.txt)
>> > +1 mvn apache-rat:check
>> > +1 no binaries (except test archives)
>> > +1 LICENSE, NOTICE
>> > +0 README refers to
>> >
>> https://commons.apache.org/proper/commons-commons-release-plugin/javadocs/api-release
>> > which is 404 Not Found (site.zip has apidocs/)
>> > +1 RELEASE-NOTES
>> > +1 mvn clean install
>> > +0 mvn repository kind of matches src? *)
>> >
>> > *) I was unable to verify that
>> > https://repository.apache.org/content/repositories/orgapachecommons-1302
>> > contained artifacts from building this RC as the Maven repo do not
>> > include the source zip/tar.gz (see principle above)
>> >
>> >
>> >
>> >
>> > Tested with:
>> >
>> > Apache Maven 3.3.9
>> > Maven home: /usr/share/maven
>> > Java version: 1.8.0_151, vendor: Oracle Corporation
>> > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
>> > Default locale: en_GB, platform encoding: UTF-8
>> > OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
>> "unix"
>> >
>> >> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
>> >> Hello all,
>> >>
>> >> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
>> RC1).
>> >>
>> >> Tag name:
>> >> commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>> >>
>> >> Commit ID the tag points at:
>> >> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
>> >>
>> >> Site:
>> >>
>> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
>> >>
>> >> Distribution files (committed at revision 24125):
>> >> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>> >>
>> >> Distribution files hashes (SHA1):
>> >> commons-release-plugin-1.0-bin.tar.gz
>> >> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>> >> commons-release-plugin-1.0-bin.zip
>> >> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>> >> commons-release-plugin-1.0-src.tar.gz
>> >> (SHA1: e48b67b70b154b7dc69914752814512225024504)
>> >> commons-release-plugin-1.0-src.zip
>> >> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>> >>
>> >> These are the Maven artifacts and their hashes:
>> >> commons-release-plugin-1.0-javadoc.jar
>> >> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>> >> commons-release-plugin-1.0-sources.jar
>> >> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>> >> commons-release-plugin-1.0-test-sources.jar
>> >> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>> >> commons-release-plugin-1.0-tests.jar
>> >> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>> >> commons-release-plugin-1.0.jar
>> >> (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>> >> commons-release-plugin-1.0.pom
>> >> (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>> >>
>> >> KEYS file to check signatures:
>> >> http://www.apache.org/dist/commons/KEYS
>> >>
>> >> Maven artifacts:
>> >> https://repository.apache.org/content/repositories/orgapachecommons-1302
>> >>
>> >> 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
>> >> 2018-01-14T03: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
>> >>
>> >
>> >
>> >
>> > --
>> > Stian Soiland-Reyes
>> > http://orcid.org/-0001-9842-971

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Gary Gregory 
Right: "Once a vote is successful, post a [RESULT] Release Foo 1.2
email to *dev@commons.apache.org
* as a reply to the original posting. This email
should contain a summary of the voters/votes that were cast, eg..." from
http://commons.apache.org/releases/prepare.html

Gary

On Tue, Jan 16, 2018 at 1:19 PM, Rob Tompkins  wrote:

> I’ll do the tally tonight (UTC-5). Should the announce only go to the dev
> list?
>
> On Jan 16, 2018, at 2:40 PM, Gary Gregory  wrote:
>
> I think you have enough VOTEs from the PMC ATM. Tally?
>
> Gary
>
> On Tue, Jan 16, 2018 at 10:17 AM, Otto Fowler 
> wrote:
>
>> Do you have a page with the verification steps and requirements?
>>
>>
>> On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com) wrote:
>>
>> Curious if anyone else wants to weigh in?
>>
>> > On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
>> wrote:
>> >
>> > +1 (Binding)
>> >
>> > (While I might disagree in principle about removing source .tar.gz and
>> > .zip from Maven repo, I say let's get the plugin released and find
>> > more bugs later! :) )
>> >
>>
>> This *should* be a configurable option. I don’t think though that it is in
>> this version of the plugin. Personally, I want the plugin to accommodate
>> any process that the project may use. So as the process changes one
>> direction or another, so should the plugin.
>>
>> > Checked:
>> >
>> > +1 gpg signatures
>> > +1 sha1, md5
>> > +1 source zip vs tar.gz
>> > +1 binary zip vs tar.gz
>> > +1 source vs git (for some reason git has duplicate LICENSE as well as
>> > LICENSE.txt)
>> > +1 mvn apache-rat:check
>> > +1 no binaries (except test archives)
>> > +1 LICENSE, NOTICE
>> > +0 README refers to
>> >
>> https://commons.apache.org/proper/commons-commons-release-
>> plugin/javadocs/api-release
>> > which is 404 Not Found (site.zip has apidocs/)
>> > +1 RELEASE-NOTES
>> > +1 mvn clean install
>> > +0 mvn repository kind of matches src? *)
>> >
>> > *) I was unable to verify that
>> > https://repository.apache.org/content/repositories/orgapache
>> commons-1302
>> > contained artifacts from building this RC as the Maven repo do not
>> > include the source zip/tar.gz (see principle above)
>> >
>> >
>> >
>> >
>> > Tested with:
>> >
>> > Apache Maven 3.3.9
>> > Maven home: /usr/share/maven
>> > Java version: 1.8.0_151, vendor: Oracle Corporation
>> > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
>> > Default locale: en_GB, platform encoding: UTF-8
>> > OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
>> "unix"
>> >
>> >> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
>> >> Hello all,
>> >>
>> >> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
>> RC1).
>> >>
>> >> Tag name:
>> >> commons-release-plugin-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-release-pl
>> ugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>> >>
>> >> Commit ID the tag points at:
>> >> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
>> >>
>> >> Site:
>> >>
>> https://dist.apache.org/repos/dist/dev/commons/commons-relea
>> se-plugin/site.zip
>> >>
>> >> Distribution files (committed at revision 24125):
>> >> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>> >>
>> >> Distribution files hashes (SHA1):
>> >> commons-release-plugin-1.0-bin.tar.gz
>> >> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>> >> commons-release-plugin-1.0-bin.zip
>> >> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>> >> commons-release-plugin-1.0-src.tar.gz
>> >> (SHA1: e48b67b70b154b7dc69914752814512225024504)
>> >> commons-release-plugin-1.0-src.zip
>> >> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>> >>
>> >> These are the Maven artifacts and their hashes:
>> >> commons-release-plugin-1.0-javadoc.jar
>> >> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>> >> commons-release-plugin-1.0-sources.jar
>> >> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>> >> commons-release-plugin-1.0-test-sources.jar
>> >> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>> >> commons-release-plugin-1.0-tests.jar
>> >> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>> >> commons-release-plugin-1.0.jar
>> >> (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>> >> commons-release-plugin-1.0.pom
>> >> (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>> >>
>> >> KEYS file to check signatures:
>> >> http://www.apache.org/dist/commons/KEYS
>> >>
>> >> Maven artifacts:
>> >> https://repository.apache.org/content/repositories/orgapache
>> commons-1302
>> >>
>> >> 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
>> >> 2018-01-14T03:00:00Z
>> >> (this is UTC time).
>> >>
>> >> 
>> >>
>> >> Cheers,
>> >> -Rob
>> >>
>> >>

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Rob Tompkins 
Pardon, I’ve been vague. I meant to ask about the release announcement. 
Typically we send those up to annou...@apache.org for our top level components. 
But, the prescient for commons-parent seems to be to only email the 
announcement to our dev list. Which do you think I should do?

> On Jan 16, 2018, at 4:15 PM, Gary Gregory  wrote:
> 
> Right: "Once a vote is successful, post a [RESULT] Release Foo 1.2 email to 
> dev@commons.apache.org as a reply to the original posting. This email should 
> contain a summary of the voters/votes that were cast, eg..." from 
> http://commons.apache.org/releases/prepare.html
> 
> Gary 
> 
>> On Tue, Jan 16, 2018 at 1:19 PM, Rob Tompkins  wrote:
>> I’ll do the tally tonight (UTC-5). Should the announce only go to the dev 
>> list?
>> 
>>> On Jan 16, 2018, at 2:40 PM, Gary Gregory  wrote:
>>> 
>>> I think you have enough VOTEs from the PMC ATM. Tally?
>>> 
>>> Gary
>>> 
 On Tue, Jan 16, 2018 at 10:17 AM, Otto Fowler  
 wrote:
 Do you have a page with the verification steps and requirements?
 
 
 On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com) wrote:
 
 Curious if anyone else wants to weigh in?
 
 > On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
 wrote:
 >
 > +1 (Binding)
 >
 > (While I might disagree in principle about removing source .tar.gz and
 > .zip from Maven repo, I say let's get the plugin released and find
 > more bugs later! :) )
 >
 
 This *should* be a configurable option. I don’t think though that it is in
 this version of the plugin. Personally, I want the plugin to accommodate
 any process that the project may use. So as the process changes one
 direction or another, so should the plugin.
 
 > Checked:
 >
 > +1 gpg signatures
 > +1 sha1, md5
 > +1 source zip vs tar.gz
 > +1 binary zip vs tar.gz
 > +1 source vs git (for some reason git has duplicate LICENSE as well as
 > LICENSE.txt)
 > +1 mvn apache-rat:check
 > +1 no binaries (except test archives)
 > +1 LICENSE, NOTICE
 > +0 README refers to
 >
 https://commons.apache.org/proper/commons-commons-release-plugin/javadocs/api-release
 > which is 404 Not Found (site.zip has apidocs/)
 > +1 RELEASE-NOTES
 > +1 mvn clean install
 > +0 mvn repository kind of matches src? *)
 >
 > *) I was unable to verify that
 > https://repository.apache.org/content/repositories/orgapachecommons-1302
 > contained artifacts from building this RC as the Maven repo do not
 > include the source zip/tar.gz (see principle above)
 >
 >
 >
 >
 > Tested with:
 >
 > Apache Maven 3.3.9
 > Maven home: /usr/share/maven
 > Java version: 1.8.0_151, vendor: Oracle Corporation
 > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
 > Default locale: en_GB, platform encoding: UTF-8
 > OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
 "unix"
 >
 >> On 11 January 2018 at 02:50, Rob Tompkins  wrote:
 >> Hello all,
 >>
 >> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
 RC1).
 >>
 >> Tag name:
 >> commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
 >>
 >> Commit ID the tag points at:
 >> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
 >>
 >> Site:
 >>
 https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
 >>
 >> Distribution files (committed at revision 24125):
 >> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
 >>
 >> Distribution files hashes (SHA1):
 >> commons-release-plugin-1.0-bin.tar.gz
 >> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
 >> commons-release-plugin-1.0-bin.zip
 >> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
 >> commons-release-plugin-1.0-src.tar.gz
 >> (SHA1: e48b67b70b154b7dc69914752814512225024504)
 >> commons-release-plugin-1.0-src.zip
 >> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
 >>
 >> These are the Maven artifacts and their hashes:
 >> commons-release-plugin-1.0-javadoc.jar
 >> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
 >> commons-release-plugin-1.0-sources.jar
 >> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
 >> commons-release-plugin-1.0-test-sources.jar
 >> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
 >> commons-release-plugin-1.0-tests.jar
 >> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
 >> commons-release-plugin-1.0.jar
 >> (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
 >> commons-release-plugin-1.0.pom
 >> (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
 >>

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Rob Tompkins 
Here’s my +1.

> On Jan 10, 2018, at 9:50 PM, Rob Tompkins  wrote:
> 
> Hello all,
> 
> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from RC1).
> 
> Tag name:
>   commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
> 
> Commit ID the tag points at:
>   2f48a0ebd07318419b4d92a7e7b594f4fca47428
> 
> Site:
>   
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
> 
> Distribution files (committed at revision 24125):
>   https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
> 
> Distribution files hashes (SHA1):
>  commons-release-plugin-1.0-bin.tar.gz
>  (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>  commons-release-plugin-1.0-bin.zip
>  (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>  commons-release-plugin-1.0-src.tar.gz
>  (SHA1: e48b67b70b154b7dc69914752814512225024504)
>  commons-release-plugin-1.0-src.zip
>  (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
> 
> These are the Maven artifacts and their hashes:
>  commons-release-plugin-1.0-javadoc.jar
>  (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>  commons-release-plugin-1.0-sources.jar
>  (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>  commons-release-plugin-1.0-test-sources.jar
>  (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>  commons-release-plugin-1.0-tests.jar
>  (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>  commons-release-plugin-1.0.jar
>  (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>  commons-release-plugin-1.0.pom
>  (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
> 
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>   https://repository.apache.org/content/repositories/orgapachecommons-1302
> 
> 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
> 2018-01-14T03: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

[RESULT][VOTE] Release Commons Release Plugin 1.0 base on RC1

2018-01-16 Thread Rob Tompkins 
The vote passes with the following +1 votes in order of appearance:

- Bruno P. Kinoshita,
- Stian Soiland-Reyes, and
- Rob Tompkins

I will perform the requisite promotion activities. Many thanks to all of those 
that weighed in on this and the ideas for improvements that can be made to the 
component. I think that we should be able accommodate most if not all of the 
suggestions at hand.

Thanks again,
-Rob

> On Jan 10, 2018, at 9:50 PM, Rob Tompkins  wrote:
> 
> Hello all,
> 
> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from RC1).
> 
> Tag name:
>   commons-release-plugin-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-release-plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
> 
> Commit ID the tag points at:
>   2f48a0ebd07318419b4d92a7e7b594f4fca47428
> 
> Site:
>   
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/site.zip
> 
> Distribution files (committed at revision 24125):
>   https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
> 
> Distribution files hashes (SHA1):
>  commons-release-plugin-1.0-bin.tar.gz
>  (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>  commons-release-plugin-1.0-bin.zip
>  (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>  commons-release-plugin-1.0-src.tar.gz
>  (SHA1: e48b67b70b154b7dc69914752814512225024504)
>  commons-release-plugin-1.0-src.zip
>  (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
> 
> These are the Maven artifacts and their hashes:
>  commons-release-plugin-1.0-javadoc.jar
>  (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>  commons-release-plugin-1.0-sources.jar
>  (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>  commons-release-plugin-1.0-test-sources.jar
>  (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>  commons-release-plugin-1.0-tests.jar
>  (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>  commons-release-plugin-1.0.jar
>  (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>  commons-release-plugin-1.0.pom
>  (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
> 
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>   https://repository.apache.org/content/repositories/orgapachecommons-1302
> 
> 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
> 2018-01-14T03: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 Release Plugin 1.0 base on RC1

2018-01-16 Thread Gary Gregory 
For an internal component like this one and commons-parent, I feel that
announcing on @dev is plenty. Users don't care and the Apache announce list
is not appropriate IMO.

Gary

On Tue, Jan 16, 2018 at 3:22 PM, Rob Tompkins  wrote:

> Pardon, I’ve been vague. I meant to ask about the release announcement.
> Typically we send those up to annou...@apache.org for our top level
> components. But, the prescient for commons-parent seems to be to only email
> the announcement to our dev list. Which do you think I should do?
>
> On Jan 16, 2018, at 4:15 PM, Gary Gregory  wrote:
>
> Right: "Once a vote is successful, post a [RESULT] Release Foo 1.2 email
> to *dev@commons.apache.org * as a reply to the
> original posting. This email should contain a summary of the voters/votes
> that were cast, eg..." from http://commons.apache.
> org/releases/prepare.html
>
> Gary
>
> On Tue, Jan 16, 2018 at 1:19 PM, Rob Tompkins  wrote:
>
>> I’ll do the tally tonight (UTC-5). Should the announce only go to the dev
>> list?
>>
>> On Jan 16, 2018, at 2:40 PM, Gary Gregory  wrote:
>>
>> I think you have enough VOTEs from the PMC ATM. Tally?
>>
>> Gary
>>
>> On Tue, Jan 16, 2018 at 10:17 AM, Otto Fowler 
>> wrote:
>>
>>> Do you have a page with the verification steps and requirements?
>>>
>>>
>>> On January 16, 2018 at 11:59:34, Rob Tompkins (chtom...@gmail.com)
>>> wrote:
>>>
>>> Curious if anyone else wants to weigh in?
>>>
>>> > On Jan 16, 2018, at 6:55 AM, Stian Soiland-Reyes 
>>> wrote:
>>> >
>>> > +1 (Binding)
>>> >
>>> > (While I might disagree in principle about removing source .tar.gz and
>>> > .zip from Maven repo, I say let's get the plugin released and find
>>> > more bugs later! :) )
>>> >
>>>
>>> This *should* be a configurable option. I don’t think though that it is
>>> in
>>> this version of the plugin. Personally, I want the plugin to accommodate
>>> any process that the project may use. So as the process changes one
>>> direction or another, so should the plugin.
>>>
>>> > Checked:
>>> >
>>> > +1 gpg signatures
>>> > +1 sha1, md5
>>> > +1 source zip vs tar.gz
>>> > +1 binary zip vs tar.gz
>>> > +1 source vs git (for some reason git has duplicate LICENSE as well as
>>> > LICENSE.txt)
>>> > +1 mvn apache-rat:check
>>> > +1 no binaries (except test archives)
>>> > +1 LICENSE, NOTICE
>>> > +0 README refers to
>>> >
>>> https://commons.apache.org/proper/commons-commons-release-pl
>>> ugin/javadocs/api-release
>>> > which is 404 Not Found (site.zip has apidocs/)
>>> > +1 RELEASE-NOTES
>>> > +1 mvn clean install
>>> > +0 mvn repository kind of matches src? *)
>>> >
>>> > *) I was unable to verify that
>>> > https://repository.apache.org/content/repositories/orgapache
>>> commons-1302
>>> > contained artifacts from building this RC as the Maven repo do not
>>> > include the source zip/tar.gz (see principle above)
>>> >
>>> >
>>> >
>>> >
>>> > Tested with:
>>> >
>>> > Apache Maven 3.3.9
>>> > Maven home: /usr/share/maven
>>> > Java version: 1.8.0_151, vendor: Oracle Corporation
>>> > Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
>>> > Default locale: en_GB, platform encoding: UTF-8
>>> > OS name: "linux", version: "4.13.0-26-generic", arch: "amd64", family:
>>> "unix"
>>> >
>>> >> On 11 January 2018 at 02:50, Rob Tompkins 
>>> wrote:
>>> >> Hello all,
>>> >>
>>> >> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
>>> RC1).
>>> >>
>>> >> Tag name:
>>> >> commons-release-plugin-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-release-pl
>>> ugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>>> >>
>>> >> Commit ID the tag points at:
>>> >> 2f48a0ebd07318419b4d92a7e7b594f4fca47428
>>> >>
>>> >> Site:
>>> >>
>>> https://dist.apache.org/repos/dist/dev/commons/commons-relea
>>> se-plugin/site.zip
>>> >>
>>> >> Distribution files (committed at revision 24125):
>>> >> https://dist.apache.org/repos/dist/dev/commons/commons-relea
>>> se-plugin/
>>> >>
>>> >> Distribution files hashes (SHA1):
>>> >> commons-release-plugin-1.0-bin.tar.gz
>>> >> (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>>> >> commons-release-plugin-1.0-bin.zip
>>> >> (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>>> >> commons-release-plugin-1.0-src.tar.gz
>>> >> (SHA1: e48b67b70b154b7dc69914752814512225024504)
>>> >> commons-release-plugin-1.0-src.zip
>>> >> (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>>> >>
>>> >> These are the Maven artifacts and their hashes:
>>> >> commons-release-plugin-1.0-javadoc.jar
>>> >> (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>>> >> commons-release-plugin-1.0-sources.jar
>>> >> (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>>> >> commons-release-plugin-1.0-test-sources.jar
>>> >> (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>>> >> commons-release-plugin-1.0-tests.jar
>>> >> (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>>> >> commons-release-plugin-1.0.jar
>>> >> (SHA1: 2

[ANNOUNCE] Apache Commons Release Plugin 1.0 Released

2018-01-16 Thread Rob Tompkins 
[This announcement is only going to the dev list.]

The Apache Commons Release Plugin team is pleased to announce the release of 
Apache
Commons Release Plugin 1.0.

The Apache Commons Release Plugin is a collection of Java based Maven mojos for 
Apache Commons
Release process. These mojos are intended to be used as a collection of steps 
to be strung
together for the purpose of removing the manual steps required to produce an 
Apache Commons Release.

Changes in this version:

o COMMONSSITE-96:   Create commons-release-component project skeleton.
o COMMONSSITE-99:   Prepare Standard Build integrations, travis, jacoco, 
checkstyle, etc.
o COMMONSSITE-97:   Documentation for commons-release-plugin.

List of changes:
http://commons.apache.org/commons-release-plugin/changes-report.html 


For complete information on Apache Commons Release Plugin, including 
instructions
on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons
Release Plugin website:

http://commons.apache.org/commons-release-plugin/index.html 


Cheers,
-Rob