Author: allee8285
Date: Thu Apr 18 20:59:01 2013
New Revision: 1469569
URL: http://svn.apache.org/r1469569
Log:
More "finalize release" updates
Modified:
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Modified:
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.mdtext?rev=1469569&r1=1469568&r2=1469569&view=diff
==============================================================================
---
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
(original)
+++
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Thu Apr 18 20:59:01 2013
@@ -276,15 +276,13 @@ Different arguments and steps are requir
$ svn add ${RELEASE}
$ svn commit -m "Commit ${RELEASE} RELEASE-NOTES,
javadoc and manual to http://openjpa.apache.org/builds";
- 6. verify that /www/openjpa.apache.org/builds/${RELEASE}/docs/manual
is populated correctly by comparing it to a previous release.
+ 6. Verify that /www/openjpa.apache.org/builds/${RELEASE}/docs/manual
is populated correctly by comparing it to a previous release.
3. Copy the distribution artifacts over to the distribution area.
1. ssh to people.apache.org and create the distribution folder
$ mkdir /www/www.apache.org/dist/openjpa/${RELEASE}
- $ chgrp -R openjpa /www/www.apache.org/dist/openjpa/${RELEASE}
- $ chmod -R g+w /www/www.apache.org/dist/openjpa/${RELEASE}
2. Update the assemblies in the distribution directory. For this,
we'll just wget copies of the released assemblies with their signatures and
hashes from the Apache repo:
@@ -296,7 +294,12 @@ Different arguments and steps are requir
Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP
files above.
- 3. Optional: Remove the previous version from /dist. Ie if you're
publishing 2.0.1 you would remove 2.0.0. Verify that the release being removed
is in the distribution archives before removing.
+ 3. Update openjpa group access
+
+ $ chgrp -R openjpa /www/www.apache.org/dist/openjpa/${RELEASE}
+ $ chmod -R g+w /www/www.apache.org/dist/openjpa/${RELEASE}
+
+ 4. Optional: Remove the previous version from /dist. Ie if you're
publishing 2.0.1 you would remove 2.0.0. Verify that the release being removed
is in the distribution archives before removing.
$ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
$ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
@@ -313,20 +316,23 @@ Different arguments and steps are requir
1. After the distribution and build files have been mirrored out to the
external sites (takes about an hour):
1. Update the
[Documentation](http://openjpa.apache.org/documentation.html) wiki page:
- * Latest release link (as needed)
-
- $ rm /www/openjpa.apache.org/docs/latest
- $ ln -fvs ../builds/${RELEASE}/apache-openjpa/docs/
/www/openjpa.apache.org/docs/latest
-
* Update the new SNAPSHOT manual and javadoc links
* Add a newly created release entry
-
+ * Update SNAPSHOT documentation source URL in
<https://svn.apache.org/repos/asf/openjpa/site/trunk/content/.htaccess>. For
example:
+
+ From
+ Redirect Permanent
/builds/apache-openjpa-2.2.2-SNAPSHOT/docs
http://ci.apache.org/projects/openjpa/2.2.x
+ to
+ Redirect Permanent
/builds/apache-openjpa-2.2.3-SNAPSHOT/docs
http://ci.apache.org/projects/openjpa/2.2.x
+
2. Update the
[Downloads](http://openjpa.apache.org/documentation.html) wiki page:
* Add the newly ${RELEASE} binary and source links to the dynamic
distributed servers
* Add the newly ${RELEASE} RELEASE.NOTE.html link.
* Update previous release links to the corresponding entry in
//archive.apache.org/dist/openjpa/*
+ 3. Push all the Wiki page changes to the openjpa.apache.org site using CMS
"Publish Site" function.
+
2. Make a blog announcement on the OpenJPA wiki.
1. FIX ME!
