Author: allee8285
Date: Thu Apr 18 15:07:23 2013
New Revision: 1469361
URL: http://svn.apache.org/r1469361
Log:
Update finalized release section.
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=1469361&r1=1469360&r2=1469361&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 15:07:23 2013
@@ -33,7 +33,11 @@ More details on releasing artifacts and
2. Click "Release Notes" link in upper right.
2. Update the RELEASE-NOTES.html based on the HTML release reports
from JIRA.
3. Review and update README.txt, CHANGES.txt, BUILDING.txt and NOTICE
if needed.
- 4. Commit any changes back to svn -
+ 4. Change Copyright to correct years:
+ * openjpa-project/src/doc/manual/manual.xml
+ * openjpa-project/CHANGES.txt
+ * openjpa-project/RELEASE.NOTES.html
+ 5. Commit any changes back to svn -
$ svn commit -m "Updating files for release."
@@ -233,47 +237,71 @@ Different arguments and steps are requir
1.
[https://repository.apache.org/index.html](https://repository.apache.org/index.html)
2. Build Promotion --> Staging Repositories
3. Select/check org.apache.openjpa-xxx and select Release.
- 2. Copy the staged site over to the openjpa/builds location on
people.apache.org.
- 1. ssh to people.apache.org
-
- $ mkdir /www/openjpa.apache.org/builds/2.0.1
- $ cp -r ~/public_html/openjpa/2.0.1/staging-site/*
/www/openjpa.apache.org/builds/2.0.1/
- $ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
-
- 2. Update the assemblies in the Downloads directory. For this, we'll
just wget copies of the released assemblies with their signatures and hashes
from the Apache repo:
-
- $ cd
/www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
- wget [--no-check-certificate]
https://repository.apache.org/content/repositories/releases/\
-
org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
- wget [--no-check-certificate]
https://repository.apache.org/content/repositories/releases/\
-
org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
-
- Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP
files above.
-
- 3. copy the RELEASE-NOTES.html to the proper location
-
- $ cd ...../2.0.1-rc1/
- $ scp openjpa-project/RELEASE-NOTES.html
[email protected]:\
- /www/openjpa.apache.org/builds/2.0.1/apache-openjpa
+
+ 2. Copy documentation contents (RELEASE.NOTES, javadoc and manual) from
the staged site over to the
+ <http://openjpa.apache.org/builds>/${RELEASE} site. The content of this
site is located on
+ <https://svn.apache.org/repos/infra/websites/production/openjpa/content>.
+ 1. Assume the following environment variable definitions (you need to
adjust to your configuration):
+
+ # Release designation
+ export RELEASE=2.2.2
+ # Location where the release candidate is built
+ export RCDIR=/root/tc/WASX/workspace/${RELEASE}-rc2
+ # OpenJPA svn user id
+ export ojUser=allee8285
+ # Temporary location where the "builds" contents are collected
+ export RELBUILDS=/tmp/${RELEASE}.builds
+
+ 2. Prepare the "check out" environment for artifact collection
+
+ rm -rf ${RELBUILDS}
+ svn co
https://svn.apache.org/repos/infra/websites/production/openjpa/content/builds
${RELBUILDS} --depth empty
+
+ mkdir ${RELBUILDS}/${RELEASE}
+ mkdir ${RELBUILDS}/${RELEASE}/apache-openjpa
+
+ 3. Collect RELEASE.NOTES.html
+
+ cd ${RELBUILDS}/${RELEASE}
+ cp ${RCDIR}/openjpa-project/RELEASE-NOTES.html
apache-openjpa
+
+ 4. Collect manual and javadoc
+
+ scp -r
${ojUser}@people.apache.org:~/public_html/openjpa/${RELEASE}/staging-site/apache-openjpa/docs
apache-openjpa/docs
+ scp -r
${ojUser}@people.apache.org:~/public_html/openjpa/${RELEASE}/staging-site/apidocs
apidocs
+
+ 5. Commit content to svn repository
+
+ cd ${RELBUILDS}
+ 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.
- 4. verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is
populated correctly by comparing it to a previous release.
+ 3. Copy the distribution artifacts over to the distribution area.
- $ rm /www/openjpa.apache.org/docs/latest
- $ ln -fvs ../builds/2.0.1/apache-openjpa/docs/
/www/openjpa.apache.org/docs/latest
+ 1. ssh to people.apache.org and create the distribution folder
- 3. Copy the distribution artifacts over to the distribution area.
+ $ 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:
+
+ $ cd /www/www.apache.org/dist/openjpa/${RELEASE}
+ $ wget [--no-check-certificate]
https://repository.apache.org/content/repositories/releases/\
+
org/apache/openjpa/apache-openjpa/${RELEASE}/apache-openjpa-${RELEASE}-source.zip
+ $ wget [--no-check-certificate]
https://repository.apache.org/content/repositories/releases/\
+
org/apache/openjpa/apache-openjpa/${RELEASE}/apache-openjpa-${RELEASE}-binary.zip
- mkdir /www/www.apache.org/dist/openjpa/2.0.1
- cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/*
/www/www.apache.org/dist/openjpa/2.0.1/
- chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
- chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
+ Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP
files above.
- 1. 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. 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
- 4. Update the [JIRA
Releases](https://issues.apache.org/jira/browse/OPENJPA) page to mark the
version as "released", and set the date to the date that the release was
approved. You may also need to make a new release entry for the next release.
+ 4. Update the [JIRA
Releases](https://issues.apache.org/jira/browse/OPENJPA) page to mark the
version as "released", and set the date to the date that the release was
approved.
+ You may also need to make a new release entry for the next release.
5. Check and update the "openjpa.version" property to the correct release
in:
@@ -281,16 +309,31 @@ Different arguments and steps are requir
openjpa-examples/openbooks/run.properties
12. Update wiki pages
- 1. After the distribution and build files have been mirrored out to the
external sites (takes about an hour), update the [Downloads](downloads.html)
and [Documentation](documentation.html) pages with the new release.
+ 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
+
+ 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/*
+
2. Make a blog announcement on the OpenJPA wiki.
1. FIX ME!
13. Announcing the release
- 1. FIX MEEEE!! After the Maven mirrors have had time to update (24 hours
to be on the safe side) and the wiki updates have
+ 1. After the Maven mirrors have had time to update (24 hours to be on the
safe side) and the wiki updates have
been exported and mirrored to the external website, then it's time to
announce the release. Make an announcement about
the release on the dev@, user@ and [mailto:[email protected]] list as
per
- [the Apache Announcement Mailing Lists
page](http://www.apache.org/foundation/mailinglists.html#foundation-announce)
-)
+ [the Apache Announcement Mailing Lists
page](http://www.apache.org/foundation/mailinglists.html#foundation-announce).
<div class="note">
Make sure you send the announcement to [email protected] from your
