Author: kwsutter
Date: Thu May 15 16:29:41 2014
New Revision: 1594968
URL: http://svn.apache.org/r1594968
Log:
Added information the branch build process
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=1594968&r1=1594967&r2=1594968&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 May 15 16:29:41 2014
@@ -7,7 +7,7 @@ Title: Apache Nexus Release Process 1.2.
We're starting to move our builds over to using the Apache Nexus repository
(repository.apache.org) for releasing SNAPSHOT and release artifacts.
More details on releasing artifacts and using Nexus can be found on the Maven
website at - <http://maven.apache.org/developers/release/apache-release.html>
-1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)
+ - Environment setup for releasing artifacts (same for SNAPSHOTs and releases)
1. Increase the default Java heap available to Maven (required for Java SE
6)
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
@@ -25,7 +25,7 @@ More details on releasing artifacts and
OS name: "linux" version: "2.6.18-348.3.1.el5xen" arch: "amd64"
Family: "unix"
[root@vega workspace]#
-2. Prepare the source for release:
+ - Prepare the source for release:
1. Cleanup JIRA so the Fix Version in issues resolved since the last
release includes this release version correctly. Also, transition any Resolved
issues to the Closed state.
2. Update the text files in a working copy of the openjpa-project subdir -
1. Update the CHANGES.txt based on the Text release reports from JIRA.
@@ -78,19 +78,19 @@ If you run into the following exception
* The openjpa source and release distribution files have the right
content.
* All jars/zips/poms have .asc (PGP signature) and md5 files
-1. For new major releases (like 2.0.0 to 2.1.0)
+ - For new major releases (like 2.0.0 to 2.1.0)
1. Create a sub-branch from which to make the release. Releasing from a
branch will allow any cosmetic changes that need to be made for the release to
be approved to be done without preventing other more disruptive advances in the
trunk from potentially causing problems with the release. It also provides a
future maintenance branch (like 2.0.x.) A branch can be made by running:
$ mvn release:branch -DbranchName=2.0.x -Dusername=svn.user
-Dpassword=svn.password
-1. Checkout a clean copy of the trunk/branch to release using command line svn.
+ - Checkout a clean copy of the trunk/branch to release using command line
svn.
1. Do not use Eclipse to do the checkout. The extra dot (.) files created
by Eclipse throws off the rat:check processing and will get included in the
source distribution.
$ svn checkout
https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
<span class="note">Make sure you use https:// protocol because the
following release:prepare step requires update to the svn repository.</span>
-5. \(Optional\) Do a dry run of the release:prepare step.
+ - \(Optional\) Do a dry run of the release:prepare step.
1. The dry run will not commit any changes back to SVN and gives you the
opportunity to verify that the release process will complete as expected. You
will be prompted for the following information :
1. Release version - take the default - (default 2.0.1)
2. SCM release tag - *DO NOT TAKE THE DEFAULT* - (default
openjpa-parent-2.0.1): : 2.0.1
@@ -118,7 +118,7 @@ created. If that doesn't help, try runni
$ mvn -Papache-release release:rollback
-6. Prepare the release
+ - Prepare the release
1. Run the "release:prepare" step for real this time. You'll be prompted
for the same version information and optionally your GPG passphrase again.
$ mvn release:prepare
-Papache-release,docbook-profile,test-derbymem,bval -DskipTests \
@@ -137,20 +137,20 @@ Different arguments and steps are requir
</div>
-7. Backup (zip or tar) your local release candidate directory in case you need
to rollback the release after the next step is performed.
+ - Backup (zip or tar) your local release candidate directory in case you
need to rollback the release after the next step is performed.
cd ..
tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
cd 2.0.1-rc1
-8. Perform the release
+ - Perform the release
1. This step will create a maven staging repository and site for use in
testing and voting. You will be prompted for your repository.apache.org and
people.apache.org password several times if you have not added server profiles
to your settings.xml. See [Release
Setup](http://openjpa.apache.org/release-setup.html) for more information.
$ mvn release:perform -Papache-release
-Duser.name=<your-apache-uid>
2. The maven-release-plugin is configured with goals "deploy site
site-deploy" and will deploy the site files to a staging-site directory on
people.apache.org.
-9. Verify the release artifacts
+ - Verify the release artifacts
1. Verify the HTML links in staging-site/index.html are correct
1. Login to people.apache.org
2. Edit public_html/openjpa/\[release\]/staging-site/index.html and
updates the followings:
@@ -171,7 +171,7 @@ Different arguments and steps are requir
4. Close the nexus staging repo
1. Select/check org.apache.openjpa-xxx and select Close.
-10. Put the release candidate up for a vote
+ - Put the release candidate up for a vote
1. Create a VOTE email thread on dev@openjpa to record votes as replies,
like -
To: dev@
@@ -232,7 +232,7 @@ Different arguments and steps are requir
2. Include a list of everyone who voted +1, 0 or -1.
-11. Finalizing a release
+ - Finalizing a release
1. Release the staged nexus artifacts -
1.
[https://repository.apache.org/index.html](https://repository.apache.org/index.html)
2. Build Promotion --> Staging Repositories
@@ -314,7 +314,7 @@ Different arguments and steps are requir
openjpa-examples/openbooks/build.properties
openjpa-examples/openbooks/run.properties
-12. Update wiki pages
+ - Update wiki pages
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:
@@ -327,12 +327,15 @@ Different arguments and steps are requir
to
Redirect Permanent
/builds/apache-openjpa-2.2.3-SNAPSHOT/docs
http://ci.apache.org/projects/openjpa/2.2.x
- 2. If new branch is created, one will need to submit a request to
infrastructure team to create a new buildbot doc build process for the new
branch. See [BuildBot Doc
Build](http://openjpa.apache.org/buildbot.tips.n.techniques.html) for tips.
+ 2. If new branch is created, one will need to submit requests to
infrastructure team to create or update the buildbot process for the new
branch. See [BuildBot Doc
Build](http://openjpa.apache.org/buildbot.tips.n.techniques.html) for doc build
tips, see the [Jenkins
wiki](http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson) for
information on the Jenkins build process. Also, reference the following JIRAs
for learning further about the process.
+
+ * Example [doc builds
JIRA](https://issues.apache.org/jira/browse/INFRA-7738)
+ * Example [Jenkins build
JIRA](https://issues.apache.org/jira/browse/INFRA-7739)
3. Update the [Downloads](http://openjpa.apache.org/downloads.html)
wiki page:
* Add the newly ${RELEASE} binary and source links to the dynamic
distributed servers
- * Add the newly ${RELEASE} RELEASE.NOTE.html link.
+ * Add the newly ${RELEASE} RELEASE-NOTES.html link.
* Update previous release links to the corresponding entry in
//archive.apache.org/dist/openjpa/*
4. Update the [Nightly
Downloads](http://openjpa.apache.org/downloads-nightly.html) wiki page:
@@ -354,7 +357,7 @@ Different arguments and steps are requir
<div class="note">
Make sure you send the announcement to [email protected] from your
[email protected]. This can be achieved using gmail by setting the "From"
-field to [email protected] instead of [email protected] when sending the
+field to [email protected] instead of [email protected] when sending the
announcement.
</div>
