[x] +1 Release these artifacts

Build passing from tag, with the commands in the body of the vote e-mail, with

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_265, vendor: Private Build, runtime: 
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-52-generic", arch: "amd64", family: "unix"

Site reports look OK. There are some SpotBugs/FindBugs issues on both latest 
release & on the RC about synchronization on Lock objects, and other issues 
that might need attention later (either to disable/suppress or to fix?). But no 
blockers for the release.

 Checked pom for version. Checked file signatures for maven (core module) and 
dist area (source/binaries), no issues. Release/notice/readme files in the dist 
area and tag look good too.

Thanks!
Bruno




    On Tuesday, 27 October 2020, 6:55:34 am NZDT, Gary Gregory 
<ggreg...@apache.org> wrote:  
 
 We have fixed a few bugs and added some enhancements since Apache Commons
VFS Project 2.6.0 was released, so I would like to release Apache Commons
VFS Project 2.7.0.

Apache Commons VFS Project 2.7.0 RC2 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2 (svn
revision 42071)

The Git tag commons-vfs-2.7.0-RC2 commit for this RC is
6fa652a97a45b7b82768b6363e5e0e5c051d6a32 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-vfs.git;a=commit;h=6fa652a97a45b7b82768b6363e5e0e5c051d6a32
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-vfs.git --branch
commons-vfs-2.7.0-RC2 commons-vfs-2.7.0-RC2

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1535/org/apache/commons/

These are the artifacts and their hashes:

/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0.jar
(SHA1: 7365f67985ee83e7608cf99af961021c562a01d5)
/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0-test-sources.jar
(SHA1: c5987449060c0aea804aa23103d2d6383d1ab276)
/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0-tests.jar
(SHA1: 0c874fe7de97cdd351f1ab769d28618768fe161a)
/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0-javadoc.jar
(SHA1: db51781c57aa44ade004fa54ca833c3b6184b69a)
/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0.pom
(SHA1: 11d08a780d86ad2f6d4fb4d25d79810b6f2ec431)
/org/apache/commons/commons-vfs2/2.7.0/commons-vfs2-2.7.0-sources.jar
(SHA1: 23b44a110dd21bc02bd48e1f942dcd3523d76138)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0.jar
(SHA1: fed7b9639da6f31e859cb6ab7befaf7cee48ebeb)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0-test-sources.jar
(SHA1: dcd9c32b4f414703501d5d60bc0b401e8dab522e)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0-javadoc.jar
(SHA1: 2cbc1fb4eca472c1ccf1cfc66f53ea1226b3b61b)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0.pom
(SHA1: 42a5f3d6de94382a38355591eb1d8b4898b5fa4a)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0-sources.jar
(SHA1: 2a1e3d1cc086c68ce7d8fe7a6aa06bf46bd083a7)
/org/apache/commons/commons-vfs2-jackrabbit2/2.7.0/commons-vfs2-jackrabbit2-2.7.0-tests.jar
(SHA1: ea233fd4179e4ec87388de4bb54f32cfbbae274f)
/org/apache/commons/commons-vfs2-distribution/2.7.0/commons-vfs2-distribution-2.7.0.pom
(SHA1: fb644241a07d51d4c885a24b08635ba1c4b90129)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0-test-sources.jar
(SHA1: f0174b6b7ba665652786bc1a6911586ee6eac747)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0.jar
(SHA1: afca8bfce4ee06139c641d77a275b4ba50f70a93)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0-javadoc.jar
(SHA1: 06b69c95938e96439428e19d354c23678db862cb)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0-tests.jar
(SHA1: dc4cbeb2827b415cd42f9efd8efeeb845483dbb5)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0-sources.jar
(SHA1: c4a389c504a0d5dcaf34ccc147f5e7afac6da9b6)
/org/apache/commons/commons-vfs2-jackrabbit1/2.7.0/commons-vfs2-jackrabbit1-2.7.0.pom
(SHA1: 61b00c1d87ef22643c4b7699a252b45349aa50bc)
/org/apache/commons/commons-vfs2-examples/2.7.0/commons-vfs2-examples-2.7.0.pom
(SHA1: 767f7444d5cef179303ea913d00b6f0de271aad7)
/org/apache/commons/commons-vfs2-examples/2.7.0/commons-vfs2-examples-2.7.0.jar
(SHA1: 83765aff0515e4af97f0d24010fcc020fedfa89e)
/org/apache/commons/commons-vfs2-examples/2.7.0/commons-vfs2-examples-2.7.0-sources.jar
(SHA1: 496cf0db0bbc2552c459dd71a53493f6f11940b2)
/org/apache/commons/commons-vfs2-examples/2.7.0/commons-vfs2-examples-2.7.0-javadoc.jar
(SHA1: 80b2c58990f5f941f9661f7e787a3c57380e7ffb)
/org/apache/commons/commons-vfs2-project/2.7.0/commons-vfs2-project-2.7.0.pom
(SHA1: 955b161dd7167d21f9e12b1b2eb1c9a17784b190)
/org/apache/commons/commons-vfs2-project/2.7.0/commons-vfs2-project-2.7.0-site.xml
(SHA1: 110d3ade254a2c7f116684d8d433345c3c34455d)

I have tested with:

mvn -V -Ptest-deploy -Prelease clean install -DskipTests
mvn -V -Ptest-deploy -Prelease -P japicmp -P jacoco site
mvn -V -Ptest-deploy -Prelease deploy
mvn -V -Ptest-deploy -Prelease site:stage

using:

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_261, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_261\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Details of changes since 2.6.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2/site/index.html
    (note some *relative* links are broken and the 2.7.0 directories are
not yet created - these will be OK once the site is deployed.)

    JApiCmp Report (compared to 2.6.0):

https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2/site/commons-vfs2/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC2/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 than 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)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate
==============================

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-vfs.git --branch
commons-vfs-2.7.0-RC2 commons-vfs-2.7.0-RC2
cd commons-vfs-2.7.0-RC2

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you
then must check.

mvn apache-rat:check

3) Check binary compatibility

Older components still use Apache Clirr:

This step is not required if the site includes a Clirr report page which
you then must check.

mvn clirr:check

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which
you then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

mvn -V clean package

You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a

5) Build the site for a multi-module project

mvn -V -Ptest-deploy -Prelease clean install -DskipTests
mvn -V -Ptest-deploy -Prelease -P japicmp -P jacoco site
mvn -V -Ptest-deploy -Prelease deploy
mvn -V -Ptest-deploy -Prelease site:stage

Check the site reports in:
- Windows: target\stagging
- Linux: target/stagging

-the end-
  

Reply via email to