commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1814769 - /commons/proper/daemon/trunk/HOWTO-RELEASE.txt
Date Thu, 09 Nov 2017 20:14:53 GMT
Author: markt
Date: Thu Nov  9 20:14:53 2017
New Revision: 1814769

Update based on my 1.1.0 RC2 experience


Modified: commons/proper/daemon/trunk/HOWTO-RELEASE.txt
--- commons/proper/daemon/trunk/HOWTO-RELEASE.txt (original)
+++ commons/proper/daemon/trunk/HOWTO-RELEASE.txt Thu Nov  9 20:14:53 2017
@@ -1,6 +1,8 @@
-How to do a Apache Commons Deamon release
+How to do a Apache Commons Daemon release
+Use Java 7.
 Check out a clean copy of commons daemon from subversion to
 make sure you don't have any lingering configure or build files.
 This will make sure that the source distribution created is clean.
@@ -18,18 +20,32 @@ Update version numbers as needed
 Do a find for all the docs which include the previous version string
 and replace it with the new version.
-TODO: explain what exactly needs to be changed.
+These include:
+ - /pom.xml                             (remove -SNAPSHOT)
+ - /src/native/unix/native/version.h    (JSVC_IS_DEV_VERION 0)
+ - TODO list other files
-Maven tasks
+Create native build scripts
+cd /src/native/unix
+sh support/
+rm -rf automate.cache
+Native build
-To build the documentation: (See
-mvn site:generate
-(Do not forget to get ../commons-build: (cd ..; svn co
+Build and sign the Windows binaries.
+Place the signed Windows binaries in:
-To deploy the documentation to the apache site:
-mvn -Dmaven.username=${} site:deploy
+Maven tasks
 To deploy the Java jars to the Nexus staging repo:
@@ -41,3 +57,9 @@ The test-deploy profile will deploy to t
 Note: do not use clean in the same invocation.
 Not sure why, but with Commons-Parent v21 this results deploying the non-Maven archives (zip
and tar.gz) as well.
 They can be deleted before closing the repo, but it is easier not to create them.
+Updating the site

View raw message