Monday, 12:00
| Make sure the #One time setup steps have been performed. - set MAVEN_OPTS=-Xmx512m (for documentation creation)
- Use Sun JDK (if possible)
- If using IBM JDK, then also set the system property test.jvm.arguments to -Xdump:none (Avoids OOM heap dumps on selected tests. These extra files throw off the rat:check processing.) For example,
Code Block |
---|
|
mvn -Dtest.jvm.arguments="-Xdump:none" ...
|
- On Windows, use a cygwin window (vs a standard DOS prompt window) for the Release processing.
|
---|
Monday, 12:01
| Create a sub-branch off of the parent 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. A branch can be made by running:
Code Block |
---|
|
$ mvn release:branch -DbranchName=1.2.x
|
|
---|
Monday, 12:02
| Checkout the branch using command line svn. - Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.
Code Block |
---|
| $ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/1.2.x 1.2.x
$ cd 1.2.x |
|
---|
Monday, 12:04
| Update the text files which are included in the release. See instructions at Update release text files for details. |
---|
|
Monday, 12:10
| Commit these changes back to the branch Code Block |
---|
| $ svn commit -m "updating text files for 1.2.0 release"
|
|
---|
Monday, 12:11
| Do a dry run of the release plugin. 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 : - The new release number (default 1.2.0)
- The SCM tag (default apache-openjpa-1.2.0) *this should be changed to just 1.2.0
- The new development version (default 1.2.1)
- optional if you have not specified a GPG passphrase in settings.xml you will be prompted for it.
Code Block |
---|
| $ mvn -Prelease,docbook-profile release:prepare -DdryRun=true
<snip>
[INFO] [release:prepare]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory: /home/mikedd/workspaces/temp/jpadev/branches/1.0.x
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "OpenJPA"? (org.apache.openjpa:openjpa-parent) 1.2.0: :
What is SCM release tag or label for "OpenJPA"? (org.apache.openjpa:openjpa-parent) openjpa-parent-1.2.0: : 1.2.0
What is the new development version for "OpenJPA"? (org.apache.openjpa:openjpa-parent) 1.2.1-SNAPSHOT: :
|
|
---|
Monday, 12:30
| Validate that the release process completed as expected. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number. If other formatting changes have been made you should rollback the release and commit the changes manually. Code Block |
---|
| $ mvn -Prelease,docbook-profile release:rollback
# make changes
$ svn commit -m "fixing formatting for 1.2.0 release" |
|
---|
Monday, 12:31
| Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful |
---|
Monday, 12:52
| Prepare the release. You'll be prompted for the version information and optionally your GPG passphrase again. Code Block |
---|
| $ mvn -Prelease release:prepare |
|
---|
Monday, 13:15
| Perform the release. This step will create a maven repository for use in testing on people.apache.org:/home/userName/public_html/openjpa/newVersion. You will may be prompted for your people.apache.org password several times if you have not added a ssh key to .authorized_keys. #One time setup#people.apache.org. Code Block |
---|
| $ mvn -Prelease,docbook-profile release:perform |
|
---|
Monday, 13:40
| Create and upload the site. This step also uploads data to people.apache.org. Code Block |
---|
|
$ cd target/checkout
$ mvn -Prelease,docbook-profile site site:deploy |
|
---|
Monday, 13:40
| Unzip the binary archive the staging site directory Code Block |
---|
|
# ssh to people.apache.org
$ cd ~/public_html/openjpa/1.2.0/staging-site
$ unzip -qq apache-openjpa/downloads/apache-openjpa-1.2.0-binary.zip
|
|
---|
Monday, 13:41
| Send an email to dev@openjpa.apache.org requesting a vote. Vote email example |
---|
Tuesday, Wednesday, Thursday
| A -1 vote does not necessarily mean that the vote must be redone however it is usually a good idea to rollback the release if a -1 vote is received. Recovering from a vetoed release |
---|
Thursday, 13:41
| If the vote passes copy the release artifacts from your home directory to the ibiblio-rsync-repository using the maven stage plugin. Code Block |
---|
| $ mvn stage:copy -Dsource="http://people.apache.org/~mikedd/openjpa/1.2.0/staging-repo" \
-Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \
-Dversion=1.2.0 \
-DtargetRepositoryId=apache.releases
|
After the stage plugin completes it's a good idea to check the permissions on the file system. Code Block |
---|
$ ssh people.apache.org
$ cd /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/openjpa/
$ ls -l openjpa-examples/1.2.0
# if you see something like the following you probably need to change the permissions.
# *-rw-r--r--* 1 mikedd apcvs 59162 Jul 23 09:34 openjpa-examples-1.2.0-javadoc.jar
$ for file in `find /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/openjpa/ -type d -iname '1.2.0'`\
do \
chmod -R g+w ${file} \
done
$ ls -l openjpa-examples/1.2.0
# Now it should look something like this
# *-rw-rw--r--* 1 mikedd apcvs 59162 Jul 23 09:34 openjpa-examples-1.2.0-javadoc.jar
|
|
---|
Thursday, 14:00
| Copy build artifacts to the openjpa/builds location on people.apache.org. Code Block |
---|
| # ssh to people.apache.org
$ cp -r ~/public_html/openjpa/1.2.0/staging-site/ /www/openjpa.apache.org/builds/1.2.0
$ chmod -R g+w /www/openjpa.apache.org/builds/1.2.0
# verify that /www/openjpa.apache.org/builds/1.2.0/docs/manual is populated correctly by comparing it to a previous release.
$ rm /www/openjpa.apache.org/docs/latest
$ ln -fvs ../builds/1.2.0/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest |
|
---|
Thursday, 14:10
| Copy the distribution files to dist on people.apache.org. Code Block |
---|
|
# ssh to people.apache.org
# verify that md5 and sha1 files were generated for the download artifacts
$ ls /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/*.md5
$ ls /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/*.sha1
# if no md5 and sha1 files are present, generate them.
# Alternatively you can copy the artifacts from the staging-repo directory the checksums are generated there.
$ md5 -q apache-openjpa-1.2.0-binary.zip > apache-openjpa-1.2.0-binary.zip.md5
$ md5 -q apache-openjpa-1.2.0-source.zip > apache-openjpa-1.2.0-source.zip.md5
$ sha1 -q apache-openjpa-1.2.0-source.zip > apache-openjpa-1.2.0-source.zip.sha1
$ sha1 -q apache-openjpa-1.2.0-binary.zip > apache-openjpa-1.2.0-binary.zip.sha1
$ mkdir /www/www.apache.org/dist/openjpa/1.2.0
$ cp -r /www/openjpa.apache.org/builds/1.2.0/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/1.2.0
$ chgrp -R openjpa /www/www.apache.org/dist/openjpa/1.2.0
$ chmod -R g+w /www/www.apache.org/dist/openjpa/1.2.0
# remove the previous version from /dist. Ie if you're publishing 1.2.1 you would remove 1.2.0.
# For this example we wouldn't remove anything, but for the next release (1.2.1) we'd do the following :
$ rm -Rf /www/openjpa.apache.org/dist/openjpa/1.2.0
|
|
---|
Thursday, 14:15 | Update the JIRA versions 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 subsequent release. |
---|
Friday, 14:15 | After the mirrors have had time to update (24 hours to be on the safe side) update the downloads page with the new release |
---|
Friday, 14:15 | Make a news announcement on the OpenJPA wiki. Note |
---|
Once the news item is made, it won't show up on the front page unless you make some minor edit to the containing page (e.g., adding a newline somewhere). |
|
---|
Friday, 14:15 | Make an announcement about the release on the users@openjpa.apache.org list (and, for major releases, on the announce@apache.org list as per the Apache Announcement Mailing Lists page). The announcement might look something like this. |
---|
Friday, 14:20 | Make an announcement for the freshmeat.net OpenJPA project (optional) |
---|
Friday, 14:30 | Have a beer and enjoy your weekend while the world's grateful programmers revel in yet another high-quality release of Apache OpenJPA! |
---|