This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-daemon.git
The following commit(s) were added to refs/heads/master by this push:
new 6ca5c2f Provide a little more detail on the release process
6ca5c2f is described below
commit 6ca5c2feabc9a5b12aff6b549b54e4acfb8f9f72
Author: Mark Thomas <[email protected]>
AuthorDate: Tue Dec 16 10:48:55 2025 +0000
Provide a little more detail on the release process
---
HOWTO-RELEASE.txt | 2 +-
src/native/windows/README.txt | 9 +++++++++
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/HOWTO-RELEASE.txt b/HOWTO-RELEASE.txt
index 0389490..d88a1d3 100644
--- a/HOWTO-RELEASE.txt
+++ b/HOWTO-RELEASE.txt
@@ -89,7 +89,7 @@ sh support/buildconf.sh
Native build
------------
-Build and sign the Windows binaries.
+Build and sign the Windows binaries. See src/native/windows/README.txt
Place the signed Windows binaries in:
target/prunsrv.exe
target/prunmgr.exe
diff --git a/src/native/windows/README.txt b/src/native/windows/README.txt
index 33eadac..178f907 100644
--- a/src/native/windows/README.txt
+++ b/src/native/windows/README.txt
@@ -52,3 +52,12 @@ Release builds must not disable the static hybrid CRT build
strategy.
It is not necessary to build a 64-bit version of prunmgr since the 32-bit
version works with both 32-bit and 64-bit services.
+
+
+Code signing
+============
+
+The Windows binaries are signed using the ASF's code signing service. For
+details of the service and instructions on how new release managers can request
+access to the service see:
+https://infra.apache.org/code-signing-access.html
