This lazy vote passes with one binding vote: - Gary Gregory (ggregory)
Gary On Sun, Jun 9, 2024 at 10:45 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > My +1 > > Gary > > On Fri, Jun 7, 2024, 9:22 AM Gary Gregory <ggreg...@apache.org> wrote: >> >> We have fixed a few bugs and added enhancements since Apache Commons >> Parent 70 was released, so I would like to release Apache Commons >> Parent 71. >> >> Apache Commons Parent 71 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1 (svn >> revision 69601) >> >> The Git tag commons-parent-71-RC1 commit for this RC is >> 3c126c964ffad9de2a9ec8fd3990da8151cf08d2 which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=3c126c964ffad9de2a9ec8fd3990da8151cf08d2 >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-parent.git >> --branch commons-parent-71-RC1 commons-parent-71-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1740/org/apache/commons/commons-parent/71/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Fri Jun 07 13:17:05 UTC 2024 >> commons-parent-71-bom.json=3d8567fccb31b93b500a36ccabd92cb394b5a3b3fe1c720e8f0cbbc69d33de4574ed7ab770c494452a164d442a10a6f1c17dd8cf484c6e111db772eeff2c13a7 >> commons-parent-71-bom.xml=644aa8971610f1c01d826db63be458c039bc88a4c6dea82138012f1280672980b7d7aa4023683aa4aa231713763bac7e7fc5bd020cdb7ba90b2e8734627c862e >> commons-parent-71-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c >> commons-parent-71-src.tar.gz=f8df28a8ab6082f4086421dea93a769b1088caa6117cb277c2f488e5ac444f088138b4f74c19abf15f25108d129e7d07fd6668b4e35d207f5e45660086383865 >> commons-parent-71-src.zip=23a47536fa075713b2b6b8c5da817eb91e7f15616deed1e7faaca98ece1ba1a78744966dbe13eb0dc8220338e72ade8e4eba0c7fb3ee1adeed98f2bce95bca0b >> org.apache.commons_commons-parent-71.spdx.json=fa611fb5cd1817b34e688ef87a5ee7b78476ef336216a16435449c7fb6a52cc5cebadf998f218146db63fa0c1e8b6b88cada954a504daf11c063e30c4a286743 >> >> I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy >> -P jacoco -P japicmp clean package site deploy' using: >> >> Details of changes since 70 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1/site/index.html >> (note some *relative* links are broken and the 71 directories are >> not yet created - these will be OK once the site is deployed.) >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1/site/rat-report.html >> >> KEYS: >> https://downloads.apache.org/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. >> >> 1a) Clone and checkout the RC tag >> >> git clone https://gitbox.apache.org/repos/asf/commons-parent.git >> --branch commons-parent-71-RC1 commons-parent-71-RC1 >> cd commons-parent-71-RC1 >> >> 1b) Download and unpack the source archive from: >> >> https://dist.apache.org/repos/dist/dev/commons/parent/71-RC1/source >> >> 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 single module project >> >> Note: Some plugins require the components to be installed instead of >> packaged. >> >> mvn site >> Check the site reports in: >> - Windows: target\site\index.html >> - Linux: target/site/index.html >> >> -the end- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
