Author: bodewig
Date: Tue Oct 11 04:16:18 2011
New Revision: 1181619
URL: http://svn.apache.org/viewvc?rev=1181619&view=rev
Log:
publish artifacts
Modified:
logging/log4net/ReleaseInstructions.txt
Modified: logging/log4net/ReleaseInstructions.txt
URL:
http://svn.apache.org/viewvc/logging/log4net/ReleaseInstructions.txt?rev=1181619&r1=1181618&r2=1181619&view=diff
==============================================================================
--- logging/log4net/ReleaseInstructions.txt (original)
+++ logging/log4net/ReleaseInstructions.txt Tue Oct 11 04:16:18 2011
@@ -183,3 +183,40 @@ Create the Release
* If the vote doesn't pass, adapt trunk and start over with tagging
the next release candidate
+
+* Once the vote passes:
+
+Publish the Release
+===================
+
+* copy the ZIPs, hashes and signatures to
+ /www/www.apache.org/dist/logging/log4net/source and
+ /www/www.apache.org/dist/logging/log4net/binaries on
+ people.apache.org respectively.
+
+* create a file README.html holding just the latest news from
+ release-notes.html and copy it to
+ /www/www.apache.org/dist/logging/log4net
+
+* grab symlinks.sh from
+ https://svn.apache.org/repos/private/committers/tools/releases/symlinks.sh
+ and run it inside /www/www.apache.org/dist/logging/log4net with the
+ current version number as its only argument, i.e.
+
+ $ symlinks.sh 1.2.11
+
+* double check all files under log4net are owned by the group logging
+ and have the correct permissions (group-writable, world-readable)
+
+* create a svn tag for the release from the release candidate tag that
+ has been accepted
+
+ $ svn cp -m "1.2.11 release has been accepted" \
+ https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.11RC1 \
+ https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.11
+
+* wait for the mirrors to catch before proceeding, this takes several
+ hours
+
+Announce the Release
+====================
