My own vote [x] +1 Release these artifacts
I had to downgrade Apache Commons Parent to 52 as I couldn't generate the site - the generated layout was old, as if it couldn't load the maven site plugin theme, and rat and jdepend both failed to run [1], but also had to override the Apache Commons Release Plugin due to errors when "detaching distribution" [2]. I left notes in the pom.xml file for the issues above, with links to the related JIRA issues. Checked signatures, manually inspected files from the dist area, closed the maven repo, reviewed the Maven generated site reports, confirmed NOTICE/LICENSE/RELEASE-NOTES.txt looked OK, and checked that JIRA/GitHub pull requests were updated correctly. For the next release I will try to: - close as many PMD/CPD issues as possible - increase coverage - fix a few bugs based on user feedback - remove these TODO's/notes from pom.xml and upgrade to commons-parent-53 Thanks! -Bruno [1] https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32 [2] https://github.com/apache/commons-imaging/blob/b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1/pom.xml#L29-L32 On Fri, 13 May 2022 at 17:26, Bruno Kinoshita <ki...@apache.org> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Imaging 1.0-alpha2 was released, so I would like to > release Apache Commons Imaging 1.0-alpha3. > > Apache Commons Imaging 1.0-alpha3 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1 > (svn revision 54478) > > The Git tag commons-imaging-1.0-alpha3-RC1 commit for this RC is > b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=b1cfcaad38de7c30f7814a5b3d80e45fe2bd9af1 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-imaging.git > --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1586/org/apache/commons/commons-imaging/1.0-alpha3/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri May 13 16:54:49 NZST 2022 > > commons-imaging-1.0-alpha3-tests.jar=0435be91af272c3d9601d1e0ff5a2746ce24e67b39678a8185b566965eaa8fc84eb86da9bea86524f75552f543eca79624ac0cfd34e1b7d178420f12542c252a > > commons-imaging-1.0-alpha3-sources.jar=9f4218c8d66d2fec168571fe68b24e2770b7c61e91c024338f0a3a5409ca2fe0b558599116f194ee01d21994f99480a37c85427e43c8d9ed91c0acb8b3d49325 > > commons-imaging-1.0-alpha3-bin.zip=dbd064f46a4336d222ccb192ede94075e972360ad8b718fb2558466c462b74434b1f2afc0ec4cf251712070bc34a39770fd355d505ea63607a9f14d0a33b98fd > > commons-imaging-1.0-alpha3-src.zip=517a134f9e5df3ba99de70dcdea081be05d23d0eb25d45ce638b374c0728ad599a5834b97663e5564f80f839a76f62cc963746d75f7badc433de426a230aff0c > > commons-imaging-1.0-alpha3-javadoc.jar=8477e036b0e09e51d9c2af01b0a8a3519d58db14eb1d46f49c512fef23d4ea9f4fb2e89e5be3ead6aa70f128578464b74608b8b832215ca71df3e2dfbd0db357 > > commons-imaging-1.0-alpha3-test-sources.jar=2ec8b641a73ad45d9df8d6daef412baa25be8ec4c9dddea1daf033ff60eea88dfd959690adce0e74c97424a77bc9c5732ddbfe8862c39d437d750fc706d54ecc > > commons-imaging-1.0-alpha3-bin.tar.gz=3c4fcf1bc61cb771b125d4134c96997f6d82dd20f053d8d229cc20cb97904bd306967db57253cc062a609fae7a091c2be1ecb36cf9bb116d3bce032edec40590 > > commons-imaging-1.0-alpha3-src.tar.gz=065b69bd337e5609750fb396175e7872d8f2d62e1e0f76c3a443c371ccbe40be16078bd17551ed15b2c918efe1417f6159dbdf158a3d8638de6510405af357e6 > > > > I have tested this with ***'mvn clean install site'*** using: > *** > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) > Maven home: /opt/apache-maven-3.8.5 > Java version: 11.0.15, vendor: Private Build, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-110-generic", arch: "amd64", family: > "unix" > *** > > Details of changes since 1.0-alpha2 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-RC1/site/index.html > (note some *relative* links are broken and the 1.0-alpha3 directories > are not yet created - these will be OK once the site is deployed.) > > CLIRR and JApiCmp reports are not being used during the alpha releases, > but will be used again in the > 1.0 release (alpha3 is expected to be the last 1.0 alpha release.) > > There are some PMD and CPD issues that will be fixed before the 1.0 > release. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/imaging/1.0-alpha3-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 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, > > Bruno P. Kinoshita, > Release Manager (using key 33C6E01240C5468C2B7A556954E2764B48A42DF0) > > The 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-imaging.git > --branch commons-imaging-1.0-alpha3-RC1 commons-imaging-1.0-alpha3-RC1 > cd commons-imaging-1.0-alpha3-RC1 > > 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 > > 6) Build the site for a multi-module project > > mvn site > mvn site:stage > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > -the end- >
