On Sat, Jan 18, 2025 at 7:57 AM sebb <seb...@gmail.com> wrote: > > Has it been released? I cannot find an ANNOUNCE email.
It looks like I forgot, sending ASAP... > > It looks as though updating to this version may require significant > changes to files used to build the site; it would be helpful to > document these in the announce email and RN. I'll point it out. All components have already been updated except Jelly IIRC. There are still bullet-proofing to do like adding XSD declarations where missing. Gary > > On Tue, 7 Jan 2025 at 20:01, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > This lazy vote passes with the following binding vote: > > > > - Gary Gregory (ggregory) > > > > TY, > > Gary > > > > On Mon, Jan 6, 2025 at 7:07 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > My +1 > > > > > > Gary > > > > > > > > > On Fri, Jan 3, 2025 at 11:07 AM Gary Gregory <garydgreg...@gmail.com> > > > wrote: > > >> > > >> We have fixed a few bugs and added enhancements since Apache Commons > > >> Parent 78 was released, so I would like to release Apache Commons Parent > > >> 79. > > >> > > >> The most important change is the migration to Doxia 2 which allows using > > >> current Maven plugins. > > >> > > >> Apache Commons Parent 79 RC2 is available for review here: > > >> https://dist.apache.org/repos/dist/dev/commons/parent/79-RC2 (svn > > >> revision 73958) > > >> > > >> The Git tag commons-parent-79-RC2 commit for this RC is > > >> b8d7c5be2505e3f669ecf202261f36511f39009b which you can browse here: > > >> > > >> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=b8d7c5be2505e3f669ecf202261f36511f39009b > > >> You may checkout this tag using: > > >> git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > >> --branch commons-parent-79-RC2 commons-parent-79-RC2 > > >> > > >> Maven artifacts are here: > > >> > > >> https://repository.apache.org/content/repositories/orgapachecommons-1798/org/apache/commons/commons-parent/79/ > > >> > > >> These are the artifacts and their hashes: > > >> > > >> #Release SHA-512s > > >> #Fri Jan 03 15:58:47 UTC 2025 > > >> commons-parent-79-bom.json=4e7fb23db62d038cf535ed679b8721ef07aa9738e9c0d14ff5412698e9d829f35232aba31b554997148a8aa87b67dfee2d7d822bb4220c8399f68afaadf1538d > > >> commons-parent-79-bom.xml=0807a3b8956729680c7477ab92bb04db6cb9615088dc941e2c9e91e8b1ae402c6f7be479c24e6a8775935e6e5bf2f7b59ec0e68ca6c79be513fe4a1ee3bcbf66 > > >> commons-parent-79-site.xml=1c4e77414868a5a026a49302efbb2b629d86f210ca2430d1996e7e540706f1ed1906d36a4118b93580d7eaec7440c70ef22dfae280e568df77ae8e165b2cc159 > > >> commons-parent-79-src.tar.gz=760c8ef251cb5812a7d8fe4d5acb33e8f7478010e01a81912915b84b83368da2cc6bb80e40abe9729369dd517f3f0ee76d6dc0dcb38103397d9dbf7ebc1fa187 > > >> commons-parent-79-src.zip=44ac8cd89cd4ff270e4ddf239a7e9134bcc5c186fa0249195ad64878648dd8204ea0cf4d141245425091186d07b2df282c012ebfcd7b2c2e8f2c190fc3ef6a11 > > >> org.apache.commons_commons-parent-79.spdx.json=f2c070ea4716ab7f3fd46f44c6cff462761d64526d5a69d15efe75629a0cced9c83305167af52d6dfab8c74ef3df4d77edd0f9ccd7d30c5f5b4c71093aedf940 > > >> > > >> I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy -P > > >> jacoco -P japicmp clean package site deploy' using: > > >> > > >> openjdk version "17.0.13" 2024-10-15 > > >> OpenJDK Runtime Environment Homebrew (build 17.0.13+0) > > >> OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing) > > >> > > >> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > > >> Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > > >> Java version: 17.0.13, vendor: Homebrew, runtime: > > >> /opt/homebrew/Cellar/openjdk@17/17.0.13/libexec/openjdk.jdk/Contents/Home > > >> Default locale: en_US, platform encoding: UTF-8 > > >> OS name: "mac os x", version: "15.2", arch: "aarch64", family: "mac" > > >> > > >> Darwin ****.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 > > >> 19:03:40 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 arm64 > > >> Docker version 27.3.1, build ce12230 > > >> > > >> Details of changes since 79 are in the release notes: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/parent/79-RC2/RELEASE-NOTES.txt > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/parent/79-RC2/site/changes.html > > >> > > >> Site: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/parent/79-RC2/site/index.html > > >> (note some *relative* links are broken and the 79 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/79-RC2/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) > > >> > > >> 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. > > >> > > >> 1a) Clone and checkout the RC tag > > >> > > >> git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > >> --branch commons-parent-79-RC2 commons-parent-79-RC2 > > >> cd commons-parent-79-RC2 > > >> > > >> 1b) Download and unpack the source archive from: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/parent/79-RC2/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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
