commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (COMMONSSITE-112) [release-plugin] should create a VOTE.txt file
Date Wed, 16 May 2018 17:28:00 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477775#comment-16477775
] 

Gary Gregory edited comment on COMMONSSITE-112 at 5/16/18 5:27 PM:
-------------------------------------------------------------------

Here is an example of the VOTE.txt generated for Commons Collection:
{noformat}
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
*** THESE ITEMS REQUIRED YOUR ATTENTION ***
To: dev@commons.apache.org
Subject: [VOTE] Release Apache Commons Collections 4.2 based on RC1

We have fixed quite a few bugs and added some significant enhancements since Apache Commons
Collections 4.1 was released, so I would like to release Apache Commons Collections 4.2.

Apache Commons Collections 4.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/collections/commons-collections4-4.2-RC1 (svn
revision svn: warning: W170000: URL 'https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1'
non-existent in revision 26904

svn: E200009: Could not display info for all targets because some targets don't exist)

The Subversion tag for this RC is here:
http://svn.apache.org/repos/asf/commons/proper/collections/tags/commons-collections4-4.2-RC1/
(svn revision XYZ2)
N.B. the SVN revision is required because SVN tags are not immutable.
***OR*** 
The Git tag for this RC is here:
https://git-wip-us.apache.org/repos/asf?p=commons-collections4.git;a=tag;h=refs/tags/commons-collections4-4.2-RC1

Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-***NNNN***/org/apache/commons/commons-collections4/4.2/

These are the Maven artifacts and their hashes in Nexus:

***
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-tests.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-tests.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.pom
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-test-sources.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-sources.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-sources.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-javadoc.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-test-sources.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-javadoc.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.pom.asc
(SHA1: ***DEADBEEF***)

(no need for .asc hashes!)

I have tested this with ***'mvn clean install site'*** using: 
***
Use the output from "mvn -version" for each combination you tested.
***

Details of changes since 4.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site
(note some *relative* links are broken and the 4.2 directories are not yet created - these
will be OK once the site is deployed.)

CLIRR OR JaCoCo Report (compared to 4.1):
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/clirr-report.html

***
Note that Clirr reports several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.

Errors reported:
- methods added to interface: OK because that does not affect binary compatibility.
- etc.
***

RAT Report:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/rat-report.html

KEYS:
https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Thank you,

Gary Gregory, 
Release Manager (using key 86FDC7E2A11262CB)
{noformat}

Note the "4.2-RC1" in the dist server location, which would be key if we ever need to create
RC for more than one version at a time.


was (Author: garydgregory):
Here is an example of the VOTE.txt generated for Commons Collection:
{noformat}
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
*** THESE ITEMS REQUIRED YOUR ATTENTION ***
To: dev@commons.apache.org
Subject: [VOTE] Release Apache Commons Collections 4.2 based on RC1

We have fixed quite a few bugs and added some significant enhancements since Apache Commons
Collections 4.1 was released, so I would like to release Apache Commons Collections 4.2.

Apache Commons Collections 4.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/collections/commons-collections4-4.2-RC1 (svn
revision svn: warning: W170000: URL 'https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1'
non-existent in revision 26904

svn: E200009: Could not display info for all targets because some targets don't exist)

The Subversion tag for this RC is here:
http://svn.apache.org/repos/asf/commons/proper/collections/tags/commons-collections4-4.2-RC1/
(svn revision XYZ2)
N.B. the SVN revision is required because SVN tags are not immutable.
***OR*** 
The Git tag for this RC is here:
https://git-wip-us.apache.org/repos/asf?p=commons-collections4.git;a=tag;h=refs/tags/commons-collections4-4.2-RC1

Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-***NNNN***/org/apache/commons/commons-collections4/4.2/

These are the Maven artifacts and their hashes in Nexus:

***
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-tests.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-tests.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.pom
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-test-sources.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-sources.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-sources.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-javadoc.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-test-sources.jar.asc
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2-javadoc.jar
(SHA1: ***DEADBEEF***)
/org/apache/commons/commons-collections4/4.2/commons-collections4-4.2.pom.asc
(SHA1: ***DEADBEEF***)

(no need for .asc hashes!)

I have tested this with ***'mvn clean install site'*** using: 
***
Use the output from "mvn -version" for each combination you tested.
***

Details of changes since 4.1 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site
(note some *relative* links are broken and the 4.2 directories are not yet created - these
will be OK once the site is deployed.)

CLIRR OR JaCoCo Report (compared to 4.1):
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/clirr-report.html

***
Note that Clirr reports several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.

Errors reported:
- methods added to interface: OK because that does not affect binary compatibility.
- etc.
***

RAT Report:
https://dist.apache.org/repos/dist/dev/commons/collections/4.2-RC1/site/rat-report.html

KEYS:
https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Thank you,

Gary Gregory, 
Release Manager (using key 86FDC7E2A11262CB)
{noformat}

> [release-plugin] should create a VOTE.txt file 
> -----------------------------------------------
>
>                 Key: COMMONSSITE-112
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-112
>             Project: Commons All
>          Issue Type: New Feature
>          Components: Commons Release Plugin
>            Reporter: Gary Gregory
>            Priority: Major
>
> It would be great if the plugin would create a VOTE.txt file based on the template [http://commons.apache.org/releases/prepare.html]
> First, we should resolve whether or not we want the site to be copied as a zip file or
as an uncompressed folder on dev.
> The steps would be, first create the release candidate. Normally, releasing an RC is
done with our new Commons Release plugin:
> {noformat}
> mvn -Duser.name=${my_apache_id} -Prelease [-Ptest-deploy] clean package site deploy
> {noformat}
> Then create the release notes, right now, with what I have, you can test like this
> {noformat}
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:vote-txt
> {noformat}
> Using a goal prefix should work after the release:
> {noformat}
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT commons-release:vote-txt
> {noformat}
> This creates a VOTE.txt file in the root folder of the project.
> I am currently testing this with Commons Collections.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message