On 20/11/2025 11:04, Gary Gregory wrote:
Hi Phil,
That would be Mark...
Thank you for preparing the release candidate. I think we'll need another RC as the release notes are for 1.4.1 in a few locations.
Yep. I was working on a Windows VM for most of the changes but did the release from my Linux desktop. Looks like I forgot to pull in the latest changes before tagging.
I'll get that fixed and produce an RC3.
- Did I miss the vote for RC1? I don't think we need to clutter Git with release tags that we did not vote on. Maybe I missed it.
RC1 was tagged and then the build failed due to RAT. Versions (and tags) are cheap so I just moved forward with RC2.
- The release notes at https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/RELEASE-NOTES.txt are for 1.4.1. - The release notes in the src zip file are also for 1.4.1. - The YYYY-MM-DD date template has not been updated in changes.xml, so the page https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/site/changes.html shows YYYY-MM-DD - Not a blocker: In the future, it might be nice to have a JApiCmp report on the site.
What do I need to do to generate one of those?
The ASC and SHA512 are OK, as is running the default Maven goal on: Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec Java version: 21.0.9, vendor: Homebrew, runtime: /opt/homebrew/Cellar/openjdk@21/21.0.9/libexec/openjdk.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac" I'll try to build natives on Windows a little later.
Tx. Mark
Gary On Thu, Nov 20, 2025 at 5:28 AM Mark Thomas <[email protected]> wrote:We have fixed a few bugs and added enhancements since Apache Commons Daemon 1.4.1 was released, so I would like to release Apache Commons Daemon 1.5.0. Apache Commons Daemon 1.5.0 RC2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2 (svn revision 80871) The Git tag commons-daemon-1.5.0-RC2 commit for this RC is 1d639f6a7ab1c825ed46881b4f8eb481448a1aa5 which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-daemon.git;a=commit;h=1d639f6a7ab1c825ed46881b4f8eb481448a1aa5 You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-daemon.git --branch commons-daemon-1.5.0-RC2 commons-daemon-1.5.0-RC2 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1882/commons-daemon/commons-daemon/1.5.0/ These are the artifacts and their hashes: commons-daemon-1.5.0.jar=aa16ad7368d5ebcf13eb2ad968643f1a558505f443399a0a1e2bfb363afe9c7686165aa5ab21c7d7a7b3494b62abb61cb5629bff088c260b00414104dec9fc25 commons-daemon-1.5.0-bin.tar.gz=c3cf8dc7a214e74e4e46489337b9335a267e9898e758aa5288c134b62c05a1b9d316f5182f69472930db9283d396fbc1d6b592f11960d0813c2ff95ddbd93e39 commons-daemon-1.5.0-bin.zip=18e531ed82f042a7b9a22a606d528d213b44e04e3e8338e29b29fbd9ae00864fe8a68999413b19f981590c34abf5454ccdb9ea10f58de62aac906d569e415859 commons-daemon-1.5.0-bin-windows.zip=74370c301a3f7a901d82b7df27676bed9fbcc9eb39e3fa529e62f4cc9671a4bce0e0a44521aca42173bba5a5f0f4f016349f65e1c577f69350f4b8459d7cfb1d commons-daemon-1.5.0-native-src.tar.gz=6912f4f0263e4901ba49fed04d5cb896e3e1261bfce56f2be6e484c5e6119d6014bfd3514be13c93f3230087b9578a704cc79b3940eb57343afa3d329ef408db commons-daemon-1.5.0-native-src.zip=e2a23815f3886dda79a6c84d106b926e455ca22eb9674224716e68d94696c6d1feffedaf6732de0ef3d5333f7e31498cd9433b048bd0733a22c3780f3235cfdd commons-daemon-1.5.0-src.tar.gz=50b855694f9ce8c76df3999114735b2539677783bdd014a0b911f8a3a3c9ff06a5f6224ba3eb529ee8137fdadcce8d2f2c2b3165e01cbf36acacb37807fe73fa commons-daemon-1.5.0-src.zip=808d37cd05e44f71b2b7b7c501896bb2f73d620a6222e0b3210fb6c05e35b01d007cfd1b22c6cda931df07b2e7f21179a96bae31cfd7e1061213abd8138dcb2a I have tested this with 'mvn' and 'mvn clean install site' using: Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) Java version: 1.8.0_462, vendor: Temurin Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "6.8.0-87-generic", arch: "amd64", family: "unix" Details of changes since 1.4.1 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/site/changes.html Site: https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/site/index.html (note some *relative* links are broken and the 1.5.0 directories are not yet created - these will be OK once the site is deployed.) RAT Report: https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-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, Mark Thomas, Release Manager (using key 10C01C5A2F6059E7) The following is intended as a helper and refresher for reviewers. Validating a release candidate ============================== These guidelines are NOT complete. Requirements: Git, Java, and Maven. You can validate a release from a release candidate (RC) tag as follows. 1a) Download and decompress the source archive from: https://dist.apache.org/repos/dist/dev/commons/daemon/1.5.0-RC2/source 1b) Check out the RC tag from git (optional) This is optional, as a reviewer must check source distributions as a minimum. git clone https://gitbox.apache.org/repos/asf/commons-daemon.git --branch commons-daemon-1.5.0-RC2 commons-daemon-1.5.0-RC2 cd commons-daemon-1.5.0-RC2 2) Checking the build All components should include a default Maven goal, such that you can run 'mvn' from the command line by itself. 2) Check Apache licenses This step is not required if the site includes a RAT report page which you then must check. This check should be included in the default Maven build, but you can check it with: mvn apache-rat:check 3) Check binary compatibility This step is not required if the site includes a JApiCmp report page which you then must check. This check should be included in the default Maven build, but you can check it with: mvn verify -DskipTests -P japicmp japicmp:cmp 4) Build the package This check should be included in the default Maven build, but you can check it with: 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 4b) Check reproducibility To check that a build is reproducible, run: mvn clean verify artifact:compare -DskipTests -Dreference.repo=https://repository.apache.org/content/repositories/staging/ '-Dbuildinfo.ignore=*/*.spdx.json' Note that this excludes SPDX files from the check. 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 Note that the project reports are created for each module. Modules can be accessed using the 'Project Modules' link under the 'Project Information' menu (see <path-to-site>/modules.html). -the end- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
