Re: [VOTE] Release Apache Commons Daemon 1.6.0 based on RC3

Mark Thomas <[email protected]> Mon, 25 May 2026 09:20:32 +0100
Newsgroups gmane.comp.jakarta.commons.devel
Message-ID <[email protected]>
On 21/05/2026 23:38, Gary D. Gregory wrote:
> All went well building the non-native code from source zip file.
> 
> I got an error building prunmgr on Windows from the native source zip file:
> 
> https://gist.github.com/garydgregory/888fd2216477d6d34709be79cbb5ad1d
> 
> Building prunsrv was OK.

That looks to be a side effect of the fix for DAEMON-472 that wasn't 
picked up during the 1.5.0 release. I'll get that fixed shortly.

Mark

> 
> Microsoft Windows [Version 10.0.26100.8246]
> Microsoft (R) Program Maintenance Utility Version 14.51.36244.0
> Microsoft (R) C/C++ Optimizing Compiler Version 19.51.36244 for x64
> Microsoft (R) Incremental Linker Version 14.51.36244.0
> 
> TY!
> Gary
> 
> On 2026/05/20 13:04:20 Mark Thomas wrote:
>> We have fixed a few bugs and added binaries for ARM64 Windows since the
>> release of Apache Commons Daemon 1.5.1, so I would like to release
>> Apache Commons Daemon 1.6.0.
>>
>> Apache Commons Daemon 1.6.0 RC3 is available for review here:
>>       https://dist.apache.org/repos/dist/dev/commons/daemon/1.6.0-RC3
>> (svn revision 84634)
>>
>> The Git tag commons-daemon-1.6.0-RC3 commit for this RC is
>> a619444697a3077149f6ea14b14e8848d5468a87, which you can browse here:
>>    
>> https://gitbox.apache.org/repos/asf?p=commons-daemon.git;a=commit;h=a619444697a3077149f6ea14b14e8848d5468a87
>> You may checkout this tag using:
>>       git clone https://gitbox.apache.org/repos/asf/commons-daemon.git
>> --branch commons-daemon-1.6.0-RC3 commons-daemon-1.6.0-RC3
>>
>> Maven artifacts are here:
>>    
>> https://repository.apache.org/content/repositories/orgapachecommons-1940/commons-daemon/commons-daemon/1.6.0/
>>
>> These are the artifacts and their hashes:
>>
>> #Release SHA-512s
>> #Wed May 20 13:38:38 BST 2026
>> commons-daemon-1.6.0-bin-windows.zip=c72cb056488cd5b4202d1b86e9d10335a9458dacc44695dd0c444f9e84839e89d395b03a5240146280c772d68b6d458cd15d3eab8fb2bc1817d4022b5b0fcedd
>> commons-daemon-1.6.0-bin.tar.gz=ddc31ac5ed6a6c2812afeb6ab193562324b9c4432b64c89d02dc9d7396b938bfdd933c422b07950ab8c633276f26e5a83b2a564a37b36d0efa9c1a5d52414480
>> commons-daemon-1.6.0-bin.zip=407528373d3fefe8edd7187736f54e74e4a188d0bbc753adf41267620fe2be0cbef4a35a812b591852324b1119187ac8eaaf29a3c2f13a9986a012474aa4421b
>> commons-daemon-1.6.0-bom.json=86ccf86e011bb4a3a8441ddc059ceb096a3230c18db412351bd8d1f5e9ccbcc7dd7cd47eabdb9dd36f45462623526cdd8ff157156eec5e171a427f51ddfbbbce
>> commons-daemon-1.6.0-bom.xml=64fa302148549171b67572edd963e1562c6bf539e52ec9e4f43d235e3c518f06ee414f683d04160bb827b30aa02201cbe34b631178f98ca898bdb9b61f907fb1
>> commons-daemon-1.6.0-javadoc.jar=7d14cfcbe67fbb3d73b0223288bce8a8ec350a665e4e5c80158b6a22afa45a3b0f7ae846d6697924c37522b3b6595b41c2227aa2bc61db05199d994b2396df63
>> commons-daemon-1.6.0-native-src.tar.gz=e408672218c03391c6ea41432135de8811894574e6cfbf182eb4c3959d06a6ffb410cd5649f40b9cd7212e4c4352de8148c74a42934679c7edef36971e0d85f8
>> commons-daemon-1.6.0-native-src.zip=d20293f691f4ff1c3f1a47984493ffa813199be3ef04a4d9f5a92a1b3aa5627d84a9f5f19d55157060a988bf048a9c0c949fff972acc2ec60fb54461f1dcae9f
>> commons-daemon-1.6.0-sources.jar=3ce4c95125e22d4dde30fcf4280f58860e739405336be84395bec56ac55b6e4606890b2bdabb566e3467637c2eda7ec55228f06b549699d2cebc01edfae36b10
>> commons-daemon-1.6.0-src.tar.gz=2eb2f1fbdd703063f7b6e43e159c81b4adf4a7d676427a059595088d76835dfa54854ea7b2aa04a1dad31c946a6b554c81846e4dfa199af726cacbcf4a210989
>> commons-daemon-1.6.0-src.zip=398e83aa23a310e96a8cbb32609d643a7fd5b109a74b7af75f600587603c2550a5870c61bf03017361b9646b1097a916873226055fe7cba6446b49f7ed120409
>> commons-daemon_commons-daemon-1.6.0.spdx.json=ea8af01cfe7d5c45f44c34a2324d938ea49aa6229982f7f01348c27edb3abeba36daedc1857b36d01bc3128d6885bcd1dc7c623f7e5b99912efe60ded89b2c0c
>>
>>
>> I have tested this with 'mvn' using:
>> ***
>> Maven home: /opt/sdkman/candidates/maven/current
>> Java version: 25.0.3, vendor: Eclipse Adoptium, runtime:
>> /opt/sdkman/candidates/java/25.0.3-tem
>> Default locale: en_GB, platform encoding: UTF-8
>> OS name: "linux", version: "6.8.0-111-generic", arch: "amd64", family:
>> "unix"
>> ***
>>
>> Details of changes since 1.5.1 are in the release notes:
>>    
>> https://dist.apache.org/repos/dist/dev/commons/daemon/1.6.0-RC3/RELEASE-NOTES.txt
>>    
>> https://dist.apache.org/repos/dist/dev/commons/daemon/1.6.0-RC3/site/changes.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.6.0-RC3/source
>>
>> 1b) Check out the RC tag from git (optional)
>>
>> This is optional,  as a reviewer must at least check source distributions.
>>
>> git clone https://gitbox.apache.org/repos/asf/commons-daemon.git
>> --branch commons-daemon-1.6.0-RC3 commons-daemon-1.6.0-RC3
>> cd commons-daemon-1.6.0-RC3
>>
>> 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]
>