+1 > On Apr 15, 2024, at 1:01 PM, Bruno Kinoshita <brunodepau...@gmail.com> wrote: > > +1 > > Thank you Gary! > >> On Mon, 15 Apr 2024 at 15:36, Gary Gregory <ggreg...@apache.org> wrote: >> >> We have fixed a few bugs and added enhancements since Apache Commons >> Imaging 1.0.0-alpha4 was released, so I would like to release Apache >> Commons Imaging 1.0.0-alpha5. >> >> Apache Commons Imaging 1.0.0-alpha5 RC1 is available for review here: >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1 >> (svn revision 68532) >> >> The Git tag commons-imaging-1.0.0-alpha5-RC1 commit for this RC is >> 6dc0ba92f62056584af40a24f6c8a8215469ca8f which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=6dc0ba92f62056584af40a24f6c8a8215469ca8f >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-imaging.git >> --branch <https://gitbox.apache.org/repos/asf/commons-imaging.git--branch> >> commons-imaging-1.0.0-alpha5-RC1 >> commons-imaging-1.0.0-alpha5-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1720/org/apache/commons/commons-imaging/1.0.0-alpha5/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Mon Apr 15 13:22:38 UTC 2024 >> >> commons-imaging-1.0.0-alpha5-bom.xml=b76ae4de3f358c9d3c47925005ba0ea76ad48c0c523e6785d34d9e106dbb2b019b43e974ceb3eff598c03e6ae507b51bf9a5b0cee6fa04664f0dd589540a359e >> >> commons-imaging-1.0.0-alpha5-bin.zip=a94f25a37942b921742765931f89d640320ce5b6d7588ecf9bfb89fa8ea64d4940f88c4062cb5621e64aa9ae18e72bed81e6f517a2695b58d91d972b1f12ed9d >> >> org.apache.commons_commons-imaging-1.0.0-alpha5.spdx.json=43cea02387f469d5b4760a5a34697f81467e7de48567767bbda494f4c25f9543d44fcaac750876aec8834c1781e706e7f7884e36bf8b321ee06bfac0742ee51d >> >> commons-imaging-1.0.0-alpha5-bom.json=79e8a06869238c75a84f817986ba090bbde0124ea885efee11f24eb2f18efc8ab5ffb9699233feb08f3dedfb89580ca702c65bcc9948be5ebcbe3a9796049721 >> >> commons-imaging-1.0.0-alpha5-src.zip=78c930ad5edc1f897f049ad357a4b32e5a1c50bd5e9c127296c2209fa22f0705d981828b45c8c4e17efaea34c3c9f68f95fd416dbd6317aeeb3e4908eec0fc50 >> >> commons-imaging-1.0.0-alpha5-tests.jar=4a371d7c4fd0f16c084533cedfaafd0eb98d229758ed3455d749bc135564504e788bcf3ceb20a5c8db29aaa837744be3e06ed29d312ffbfbebfa32ff4030c9ce >> >> commons-imaging-1.0.0-alpha5-test-sources.jar=9cc2712d43a5f7d3591940a20dde807730cf0c9e9e74d3105b487f6929f3df5635e4499c9c174550516779cad02b44c7b853c971b9f0a2c206c5357a2d95345d >> >> commons-imaging-1.0.0-alpha5-src.tar.gz=fe6c8b94fecae6a694f22ec10aafe20dd4cac2fcc3811f87ac9ac5d51df11f528fc550f0e7e1e336f900cd8e92a80dedc8c3b00ff31c6e4fb03075d86c19dd3c >> >> commons-imaging-1.0.0-alpha5-javadoc.jar=4bd1c9229e443a8367fbf1402d99cc6fbf2a7f159903ddf34edb46de4d02e91f900cd3c8f9cea6c400da1c62184320c9d71729a5259748d9896cb15f5e76b530 >> >> commons-imaging-1.0.0-alpha5-sources.jar=ee27d8161b2b2b93d26b44153b319a790bb0227894cf9ab241182f02f51e2b499911253cbf0f6deef60964559bbb31414e5ee695916ef8275482d11a51b4de1d >> >> commons-imaging-1.0.0-alpha5-bin.tar.gz=ad98e5b49cfc6382c341af86ae2011da0587354dd45a7427a0507310d878b618d790ed6fc6cfdfd610801699015db1d46668a3d1eed79c5977ce00da37c2d602 >> >> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P >> jacoco -P japicmp clean package site deploy ' using: >> >> openjdk version "17.0.10" 2024-01-16 >> OpenJDK Runtime Environment Homebrew (build 17.0.10+0) >> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) >> >> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) >> Maven home: /usr/local/Cellar/maven/3.9.6/libexec >> Java version: 17.0.10, vendor: Homebrew, runtime: >> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" >> >> Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 >> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 >> >> Details of changes since 1.0.0-alpha4 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/index.html >> (note some *relative* links are broken and the 1.0.0-alpha5 >> directories are not yet created - these will be OK once the site is >> deployed.) >> >> JApiCmp Report (compared to 1.0.0-alpha4): >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/japicmp.html >> This is an alpha release with one API break. >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-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-imaging.git >> --branch <https://gitbox.apache.org/repos/asf/commons-imaging.git--branch> >> commons-imaging-1.0.0-alpha5-RC1 >> commons-imaging-1.0.0-alpha5-RC1 >> cd commons-imaging-1.0.0-alpha5-RC1 >> >> 1b) Download and unpack the source archive from: >> >> >> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-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 >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
