You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2016/04/17 16:16:57 UTC
[VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
This is a VOTE by LAZY consensus to release Commons Build Plugin 1.6
based on RC1
The changes from 1.5 are:
Added new download-page layout property:
set this to 'version' to use a single directory of the form
commons-build-plugin-1.6 rather than binaries/source
This VOTE is open for at least 72 hours until Apr 20 2016 15:00 UTC
The files:
https://repository.apache.org/content/repositories/orgapachecommons-1152/org/apache/commons/commons-build-plugin/1.6/
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-sources.jar
(SHA1: b0482b7becb86c6e1ba5f18e6b513c7bd0621e58)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-test-sources.jar
(SHA1: 6fb7fb9d5f3b228003be8d12dae1de7297d8cbe0)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.zip
(SHA1: e899b282253222aca7d0cca160c56d0d211a8fd4)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-javadoc.jar
(SHA1: 9a5b91264e979896b4d8df565d00feaafdd69318)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.jar
(SHA1: 46a803ec284c186039063c4826a22446e1bbc69e)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-tests.jar
(SHA1: ee5dfcd78cbdd7e140ebd77e7599d88bed19a37b)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.pom
(SHA1: c4213ebdeaafda42e7056ca23cbde8a24149e081)
/org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.tar.gz
(SHA1: 6ad8957d718de2ae14135f369f18b698e274411e)
The tag:
https://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/tags/commons-build-plugin-1.6-RC1
(r1739618)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by sebb <se...@gmail.com>.
On 18 April 2016 at 22:16, Stian Soiland-Reyes <st...@apache.org> wrote:
> On 18 Apr 2016 4:47 p.m., "sebb" <se...@gmail.com> wrote:
>
>> Using lazy votes for this was was agreed by the PMC a while back.
>
> Ah, I thought as it had its own website,
It has a page on the main website, like Commons Parent.
> (earlier) downloads
I'd never really noticed those before, but it does seem to have most
versions represented.
> and Maven Central artifacts it was one of the releases of Apache Commons.
It's released to Maven Central to make it easier to use as a plugin.
> Perhaps if it is only for internal project use it should not be mirrored to
> Maven Central (e.g. kept in a separate Nexus area - perpetual SNAPSHOT) -
This would make it quite awkward to use.
> or it should be treated as a proper release (even if it happens to be a bit
> exotic for non-Commons users), in which case the usual checks and balances
> apply.
>
>> > I notice this RC is 'straight to Maven' - but this should also be
> released to
>> >
> https://dist.apache.org/repos/dist/release/commons/commons-build-plugin/source/
>> >
>> > (BTW: 1.5 is missing there)
>>
>> The build plugin is entirely optional, and only intended for use by
>> Commons Developers.
>
> So none of the components depend on the build plugin as part of their
> pom.xml build? (Only on command line or in a -Prelease profile?)
No, it's only used to create various files.
These can also be created manually, but it's easier to use the plugin.
> (Sorry, I haven't checked)
>
>> Note we haven't released Commons parent POM there either.
>> If anything, that is a more deserving case for a dist release.
>
> Yes, even though the parent pom is a self-contained file, I would support
> such a move for consistency reasons and to (if ever so slightly) reduce
> reliance on Maven Central. (See NPM usecase:
> http://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ )
I cannot see that being relevant here.
> (It could be argued that everything should be source released also in the
> Nexus repository, and that it should be treated as official as
> dist.apache.org in the ASF policy. I think that is general practice in many
> projects, but then we still need to keep a copy of the hashes from the
> closed staging repo in the VOTE thread, as the staging repo disappears
> after publishing. We would then need more official mirrors)
>
>> It's not clear to me whether it is necessary to use for build tools.
>
> That depends if its needed for third party building or not.
No it's not needed.
The files it creates are included in the source release of the
projects to which they belong.
> In theory I
> should be able to grab whatever I need from dist.apache.org (and archive)
> to verify and build anything under org.apache and commons* in Maven
> Central. Obviously for other Maven Central dependencies I would need to do
> the same from their upstream sources.
>
> This is what Linux distributions like Debian do - with their own mirroring
> and patching thrown into the mix.
>
> Source code can also be accessed on demand from svn/git, but it is
> currently ASF policy that the source code tar/zip on the dist mirrors are
> the Gold Standard after a VOTE - I don't know how much leeway Commons PMC
> have here, but I found it confusing that an older version 1.4 was on dist,
> but not 1.5, even though 1.5 is in Central and on the website.
>
> I think it's OK to not release something that is only needed say for
> updating a Commons components website (as is the main purpose of this
> particular plugin) or the release process, but then the internal tool
> should not be distributed as "released" itself, as that implies something
> more within ASF. (e.g. that we have checked the license headers :))
>
> BTW, you are free to ignore my -1 - this is a just my opinion flopping in
> from the side corner! ;))
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 18 Apr 2016 4:47 p.m., "sebb" <se...@gmail.com> wrote:
> Using lazy votes for this was was agreed by the PMC a while back.
Ah, I thought as it had its own website, (earlier) downloads and Maven
Central artifacts it was one of the releases of Apache Commons.
Perhaps if it is only for internal project use it should not be mirrored to
Maven Central (e.g. kept in a separate Nexus area - perpetual SNAPSHOT) -
or it should be treated as a proper release (even if it happens to be a bit
exotic for non-Commons users), in which case the usual checks and balances
apply.
> > I notice this RC is 'straight to Maven' - but this should also be
released to
> >
https://dist.apache.org/repos/dist/release/commons/commons-build-plugin/source/
> >
> > (BTW: 1.5 is missing there)
>
> The build plugin is entirely optional, and only intended for use by
> Commons Developers.
So none of the components depend on the build plugin as part of their
pom.xml build? (Only on command line or in a -Prelease profile?)
(Sorry, I haven't checked)
> Note we haven't released Commons parent POM there either.
> If anything, that is a more deserving case for a dist release.
Yes, even though the parent pom is a self-contained file, I would support
such a move for consistency reasons and to (if ever so slightly) reduce
reliance on Maven Central. (See NPM usecase:
http://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ )
(It could be argued that everything should be source released also in the
Nexus repository, and that it should be treated as official as
dist.apache.org in the ASF policy. I think that is general practice in many
projects, but then we still need to keep a copy of the hashes from the
closed staging repo in the VOTE thread, as the staging repo disappears
after publishing. We would then need more official mirrors)
> It's not clear to me whether it is necessary to use for build tools.
That depends if its needed for third party building or not. In theory I
should be able to grab whatever I need from dist.apache.org (and archive)
to verify and build anything under org.apache and commons* in Maven
Central. Obviously for other Maven Central dependencies I would need to do
the same from their upstream sources.
This is what Linux distributions like Debian do - with their own mirroring
and patching thrown into the mix.
Source code can also be accessed on demand from svn/git, but it is
currently ASF policy that the source code tar/zip on the dist mirrors are
the Gold Standard after a VOTE - I don't know how much leeway Commons PMC
have here, but I found it confusing that an older version 1.4 was on dist,
but not 1.5, even though 1.5 is in Central and on the website.
I think it's OK to not release something that is only needed say for
updating a Commons components website (as is the main purpose of this
particular plugin) or the release process, but then the internal tool
should not be distributed as "released" itself, as that implies something
more within ASF. (e.g. that we have checked the license headers :))
BTW, you are free to ignore my -1 - this is a just my opinion flopping in
from the side corner! ;))
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by sebb <se...@gmail.com>.
On 18 April 2016 at 13:43, Stian Soiland-Reyes <st...@apache.org> wrote:
> I don't think we can do lazy release votes (even for an "internal" component):
>
> http://www.apache.org/dev/release.html#approving-a-release
Using lazy votes for this was was agreed by the PMC a while back.
>
> I notice this RC is 'straight to Maven' - but this should also be released to
> https://dist.apache.org/repos/dist/release/commons/commons-build-plugin/source/
>
> (BTW: 1.5 is missing there)
The build plugin is entirely optional, and only intended for use by
Commons Developers.
Note we haven't released Commons parent POM there either.
If anything, that is a more deserving case for a dist release.
It's not clear to me whether it is necessary to use for build tools.
I guess that needs to be checked with Legal.
>
> Here is my vote:
>
> -1 (non-binding)
>
> Checked:
> +1 mvn clean install (from svn tag)
> -1 apache-rat:check fails on
> src/main/resources/commons-xdoc-templates/download-page-body.xml and
> src/main/resources/commons-xdoc-templates/download-page-foot.xml
> -1 https://dist.apache.org/repos/dist/dev/commons/ area missing
> (unclear which source release we are voting over)
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T16:41:47+00:00)
> Maven home: /home/stain/software/maven
> Java version: 1.8.0_72-internal, 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: "3.16.0-67-generic", arch: "amd64", family: "unix"
>
> On 17 April 2016 at 15:16, sebb <se...@gmail.com> wrote:
>> This is a VOTE by LAZY consensus to release Commons Build Plugin 1.6
>> based on RC1
>>
>> The changes from 1.5 are:
>>
>> Added new download-page layout property:
>> set this to 'version' to use a single directory of the form
>> commons-build-plugin-1.6 rather than binaries/source
>>
>> This VOTE is open for at least 72 hours until Apr 20 2016 15:00 UTC
>>
>> The files:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1152/org/apache/commons/commons-build-plugin/1.6/
>>
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-sources.jar
>> (SHA1: b0482b7becb86c6e1ba5f18e6b513c7bd0621e58)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-test-sources.jar
>> (SHA1: 6fb7fb9d5f3b228003be8d12dae1de7297d8cbe0)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.zip
>> (SHA1: e899b282253222aca7d0cca160c56d0d211a8fd4)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-javadoc.jar
>> (SHA1: 9a5b91264e979896b4d8df565d00feaafdd69318)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.jar
>> (SHA1: 46a803ec284c186039063c4826a22446e1bbc69e)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-tests.jar
>> (SHA1: ee5dfcd78cbdd7e140ebd77e7599d88bed19a37b)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.pom
>> (SHA1: c4213ebdeaafda42e7056ca23cbde8a24149e081)
>> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.tar.gz
>> (SHA1: 6ad8957d718de2ae14135f369f18b698e274411e)
>>
>> The tag:
>>
>> https://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/tags/commons-build-plugin-1.6-RC1
>> (r1739618)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 18 Apr 2016 4:48 p.m., "sebb" <se...@gmail.com> wrote:
> > (I would still say -1 until the RC is on dist.apache.org)
>
> I'm not convinced it's necessary.
Agreed, as you have provided hashes, so its not necessary to upload also to
dev/commons on dist, although that is the practice for other component
release candidates.
I just wanted to check if it will go to dist after the release VOTE is
passed, and if so, what goes there.
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by sebb <se...@gmail.com>.
On 18 April 2016 at 13:53, Stian Soiland-Reyes <st...@apache.org> wrote:
> On 18 April 2016 at 13:43, Stian Soiland-Reyes <st...@apache.org> wrote:
>
>> -1 apache-rat:check fails on
>> src/main/resources/commons-xdoc-templates/download-page-body.xml and
>> src/main/resources/commons-xdoc-templates/download-page-foot.xml
>
>
> These are not really XML files, but templates to be inserted in XML
> files - and it would therefore be weird for them to have
> the standard ASF file header.
>
> I added them as apache-rat excludes to pom.xml in svn trunk.
>
> (I would still say -1 until the RC is on dist.apache.org)
I'm not convinced it's necessary.
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by Stian Soiland-Reyes <st...@apache.org>.
On 18 April 2016 at 13:43, Stian Soiland-Reyes <st...@apache.org> wrote:
> -1 apache-rat:check fails on
> src/main/resources/commons-xdoc-templates/download-page-body.xml and
> src/main/resources/commons-xdoc-templates/download-page-foot.xml
These are not really XML files, but templates to be inserted in XML
files - and it would therefore be weird for them to have
the standard ASF file header.
I added them as apache-rat excludes to pom.xml in svn trunk.
(I would still say -1 until the RC is on dist.apache.org)
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE][LAZY] Release Commons Build Plugin 1.6 based on RC1
Posted by Stian Soiland-Reyes <st...@apache.org>.
I don't think we can do lazy release votes (even for an "internal" component):
http://www.apache.org/dev/release.html#approving-a-release
I notice this RC is 'straight to Maven' - but this should also be released to
https://dist.apache.org/repos/dist/release/commons/commons-build-plugin/source/
(BTW: 1.5 is missing there)
Here is my vote:
-1 (non-binding)
Checked:
+1 mvn clean install (from svn tag)
-1 apache-rat:check fails on
src/main/resources/commons-xdoc-templates/download-page-body.xml and
src/main/resources/commons-xdoc-templates/download-page-foot.xml
-1 https://dist.apache.org/repos/dist/dev/commons/ area missing
(unclear which source release we are voting over)
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /home/stain/software/maven
Java version: 1.8.0_72-internal, 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: "3.16.0-67-generic", arch: "amd64", family: "unix"
On 17 April 2016 at 15:16, sebb <se...@gmail.com> wrote:
> This is a VOTE by LAZY consensus to release Commons Build Plugin 1.6
> based on RC1
>
> The changes from 1.5 are:
>
> Added new download-page layout property:
> set this to 'version' to use a single directory of the form
> commons-build-plugin-1.6 rather than binaries/source
>
> This VOTE is open for at least 72 hours until Apr 20 2016 15:00 UTC
>
> The files:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1152/org/apache/commons/commons-build-plugin/1.6/
>
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-sources.jar
> (SHA1: b0482b7becb86c6e1ba5f18e6b513c7bd0621e58)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-test-sources.jar
> (SHA1: 6fb7fb9d5f3b228003be8d12dae1de7297d8cbe0)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.zip
> (SHA1: e899b282253222aca7d0cca160c56d0d211a8fd4)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-javadoc.jar
> (SHA1: 9a5b91264e979896b4d8df565d00feaafdd69318)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.jar
> (SHA1: 46a803ec284c186039063c4826a22446e1bbc69e)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-tests.jar
> (SHA1: ee5dfcd78cbdd7e140ebd77e7599d88bed19a37b)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6.pom
> (SHA1: c4213ebdeaafda42e7056ca23cbde8a24149e081)
> /org/apache/commons/commons-build-plugin/1.6/commons-build-plugin-1.6-src.tar.gz
> (SHA1: 6ad8957d718de2ae14135f369f18b698e274411e)
>
> The tag:
>
> https://svn.apache.org/repos/asf/commons/proper/commons-build-plugin/tags/commons-build-plugin-1.6-RC1
> (r1739618)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org