Page edited by Donald Woods

Releasing OpenJPA

These instructions guide the release manager through the steps of making an official OpenJPA release.

Work in progress. Times are just guesses and some information may be missing.

Prerequisites

// TODO MDD Still may need some work...

You should read the OpenJPA Release Policy to decide on the name of the new release, based on the content.
You should read the Apache Release FAQ
You must have shell access to people.apache.org
You must have the following utilities installed on your local machine and available in your path:
- Java SE 5.0 (for 1.2.x and 1.3.x) or Java SE 6 (for 2.0.x) (prefer Sun JDK over IBM JDK)
- Maven 2 (at least version 2.0.10)
- ssh (cygwin covers this on Windows)
- gnupg (cygwin covers this on Windows)
For Windows users, install Cygwin in addition to the above utilities
- Make sure the Net/openssh and Utils/gnupg packages are installed that come with Cygwin installation.

Tasks that need to be performed for each release

The example below uses 1.2.x as the new branch and 1.2.0 as the new release.

Monday, 12:00

Make sure the One time setup steps have been performed.

set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m (especially for Java SE 6)
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,
```
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

??? For new major releases (like 2.0.0) 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:

$ mvn release:branch -DbranchName=1.2.x

Monday, 12:02

Checkout the trunk/branch to release 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.
```
 $ 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

 $ 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.

$ 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.

$ 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

verify signatures Verifying release signatures
run examples. Running OpenJPA Examples
if you have access to the TCK, run it Running the TCK

Monday, 12:52

Prepare the release. You'll be prompted for the version information and optionally your GPG passphrase again.

 $ mvn -Dmaven.test.execute=false -Prelease release:prepare

For the 2.0.x code, different steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See http://jira.codehaus.org/browse/MJAR-68 and http://jira.codehaus.org/browse/MRELEASE-285.

 $ mvn -Dmaven.test.execute=false -Prelease release:prepare 
 $ mvn clean install -Dtest=false -DfailIfNoTests=false -Dmaven.test.execute=false 
 $ mvn -Dmaven.test.execute=false -Prelease release:prepare

Monday, 13:12

Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version. For example if the new version is 1.2.2 you shouldn't see 1.2.1 in the file.
Backup (zip or tar) your local directory in case you need to rollback the release.

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.

$ mvn -Prelease,docbook-profile release:perform

For the 2.0.x code, you'll need to checkout, build and deploy the code w/o using the release plugin, due to the test-jar issues.

$ mvn clean install -Dtest=false -DfailIfNoTests=false -Dmaven.test.execute=false 
$ mvn deploy clean install -Dtest=false -DfailIfNoTests=false -Dmaven.test.execute=false -Prelease,docbook-profile

Monday, 13:40

Create and upload the site. This step also uploads data to people.apache.org.
For 1.x releases:

 
$ cd target/checkout

For all releases:

$ mvn -Prelease,docbook-profile site site:deploy

Monday, 13:40

Unzip the binary archive the staging site directory

# 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 [email protected] 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.

 $ 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.

$ 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.

# 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.

 
# 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.
for file in `ls . ` 
do 
md5 -q ${file} > ${file}.md5
sha1 -q ${file} > ${file}.sha1
done

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 and Documentation pages with the new release

Friday, 14:15

Make a news announcement on the OpenJPA wiki.

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 [email protected] list (and, for major releases, on the [email protected] 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!

One time setup

These setup steps only need to be performed on a particular machine once.

Developers using Linux workstations can skip over the references to Cygwin. If using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.

Create and install a SSH key

1 Open a shell window. If using Windows, open a cygwin window.

Use ssh-keygen to create an SSH key.

$ ssh-keygen -t dsa

Program defaults should be fine. No passphrase is required for the ssh key generation. The keys will be saved in ~/.ssh/id_dsa (private) and ~/.ssh/id_dsa.pub (public).
See Authenticating By Public Key (OpenSSH) for a good description on why and how to perform this task.

scp your SSH public key ~/.ssh/id_dsa.pub created in last step to ~/id_dsa.pub on people.apache.org.

 
$ cd ~/.ssh
$ scp id_dsa.pub <your userid>@people.apache.org:id_dsa.pub 
$ You will be prompted for your password.

Use ssh to login to people.apache.org

$ cd ~
$ ssh <your userid>@people.apache.org

At this point, you will still be prompted for your password.

Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.

$ mkdir ~/.ssh
$ chmod 700 ~/.ssh

Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.

$ mv ~/id_dsa.pub ~/.ssh/authorized_keys
$ chmod 600 ~/.ssh/authorized_keys

Each public key in the authorized_keys spans only one line.
- For example: "ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107"
'#' in the first column is a comment line.

7 Exit out of this ssh session.

Start a new ssh session. No login should be required this time due to the private ssh key on your local box matching up with the public ssh key in your home directory (~/.ssh).

$ ssh <your userid>@people.apache.org

If you are still prompted for a password, then you have not set up the ssh keys properly. Review the steps above and ensure that all of the steps were followed properly. Or, maybe the instructions are still not quite right and they still need some adjusting. In that case, please update the instructions accordingly.

Create a GPG key

1 Open a shell window. If using Windows, open a cygwin window.

Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).

$ gpg --gen-key

The program's default values should be fine. For the "Real Name" enter your full name (ie. Stan Programmer). For the "e-mail address" enter your apache address (ie. [email protected]). You will also be required to enter a "passphrase" for the GPG key generation. Keep track of this as you will need this for the Release processing.

The generated keys are stored in $HOME/.gnupg or %HOME%\Application Data\gnupg subdirectory.
Save the content in this subdirectory to a safe media. This contains your private key used to sign all the OpenJPA release materials.

3 Backup your cygwin home directory to another media

Add your public key to https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS and http://www.apache.org/dist/openjpa/KEYS. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the OpenJPA releases.

$ gpg --list-sigs <Real Name> && gpg --armor -- export <Real Name>

The https://svn.apache.org/repos/asf/openjpa/site/docs/KEYS file is updated via normal svn commit procedures. How the http://www.apache.org/dist/openjpa/KEYS file gets updated is still a mystery to me...

5 Following the instructions in http://people.apache.org/~henkp/trust/ and ask someone in the OpenJPA project to sign your public key.

6 Submit your public key to a key server. E.g. http://pgp.surfnet.nl:11371/ or http://pgp.mit.edu/

Update Maven settings for our servers

1 Create a settings.xml under .m2 (in your Document and Settings folder in Windows)

settings.xml

<settings xmlns="http://maven.apache.org/POM/4.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    <servers>
       <server>
          <id>people.apache.org</id>
          <username>$USERNAME</username>
          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
          <directoryPermissions>775</directoryPermissions>
          <filePermissions>644</filePermissions>
       </server>
    </servers>    
</settings>

$USERNAME is the remote username on people.apache.org, not your local userid.
$PATH_TO_PRIVATE_KEY is the path to the private key generated for ssh. E.g. /home/yourLocalUserId/.ssh/id_dsa. For Windows' cygwin users, you will need to enter the full cygwin path: /cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_dsa.
You can also enter a PGP passphrase stanza: <passphrase>..</passphrase>. If you don't use this in your settings.xml file, then you will be prompted for it during the Release processing.

Expose a copy of known hosts to Maven

Is this step even necessary? Due to the question mark below without an explanation of the new location for this alternate .ssh folder, I never performed these steps. And, the release process still seemed to work okay for me... The next person to use these instructions can verify whether any tricks had to be played with the .ssh folders...

1	From cygwin, ssh to people.apache.org, save the public key if prompted, and exit
	cygwin will save the known hosts to your `~/.ssh` folder, but the script cannot access it there (from Windows)
2	From cygwin (not Windows) create another `.ssh` folder at
3	Copy the `known_hosts` file to the new `.ssh` folder

Troubleshooting

Space Character in Build Root Path

Description	If there are spaces in the path to the build root subdirectory, the maven task uses to generate the revision number for the org.apache.openjpa.revision.properties yields incorrect data. For example: org.apache.openjpa.revision.properties revision.number=Type 'svnversion --help' for usage. openjpa.version=1.0.1
Solution	Rename the path and remove all spaces.

Merging local repository to remote repository in Cygwin/Windows

Description

The "maven-stage-plugin" is very sensitive to the parameters being passed to it, i.e. the source and target URL properties. When this plugin is used under Cygwin, make sure the following practices are used:

Use absolute path in the find command's root directory.
Problem symptom:

$ find . -name m2-repository -not -path "*openjpa-project*" \
    -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
    -Dsource=file://{} -Dtarget=scp://[email protected]/www/people.apache.org/repo/m2-ibiblio-rsync-repository \
    -Dversion=1.0.1 \;
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'stage'.
........
[INFO] Downloading file from the source repository:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying repository from file://./openjpa-all/target/site/m2-repository to \
       scp://[email protected]/www/people.apache.org/repo/m2-ibiblio-rsync-repository

Quote and use the drive name in the path.
Problem symptom:

$ find /cygdrive/c/OpenJPA.1.0.1.Release/1.0.1 -name m2-repository -not -path "*openjpa-project*" \
    -exec mvn -f /cygwin/c/tmp/maven-stage-plugin/pom.xml stage:copy \
    -Dsource=file://{} -Dtarget=scp://[email protected]/www/people.apache.org/repo/m2-ibiblio-rsync-repository \
    -Dversion=1.0.1 \;
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'stage'.
........
[INFO] Downloading file from the source repository:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying repository from file:///cygdrive/c/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository to
       scp://[email protected]/www/people.apache.org/repo/m2-ibiblio-rsync-repository

Embedded error: Could not read from file: c:\cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository
\cygdrive\c\OpenJPA.1.0.1.Release\1.0.1\openjpa-all\target\site\m2-repository (Access is denied.)

Specify the people.apache.org user id in the target property.
Problem symptom:

$ find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path "*openjpa-project*" \
   -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy 
   -Dsource=file://{} -Dtarget=scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository \
   -Dversion=1.0.1 \;
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'stage'.
[INFO] ----------------------------------------------------------------------------
........
[INFO] Downloading file from the source repository: /org/apache/openjpa/openjpa/maven-metadata.xml.sha1
[INFO] Downloading metadata from the target repository.
Password:: *********
........
Password:: *********
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying repository from file://c:/OpenJPA.1.0.1.Release/1.0.1/openjpa-all/target/site/m2-repository to \
       scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository

Solution

As recommended in the descriptions.

For example:

find "c:/OpenJPA.1.0.1.Release/1.0.1" -name m2-repository -not -path "*openjpa-project*" \
    -exec mvn -f "c:/tmp/maven-stage-plugin/pom.xml" stage:copy \
    -Dsource=file://{} \
    -Dtarget=scp://[email protected]/www/people.apache.org/repo/m2-ibiblio-rsync-repository \
    -Dversion=1.0.1 \;

Cygwin/Windows File Path

Description	For Cygwin/Windows user: file and folder path names using drive identifier (e.g. `C:\OpenJPA Release\1.0.1` ) in commands can be expressed as `/cygwin/c/OpenJPA Release/1.0.1/`. This form of path name specification may have inconsistent and undesirable behaviors.
Solution	Consistently use the following naming conventions: Continue to use the Windows form of path name, e.g. `C:\a\b\c` Use `'/'` instead of `'\'` character as file separator, e.g. `C:/a/b/c` Quote all path name using `'"'` character, e.g. "`C:/a/b/c`" Avoid using space characters in path name, e.g. "`C:/OpenJPA.Release/1.0.1`"

"Too many unapproved licenses:"

Description

Encounter the "Too many unapproved licenses:" message while running the "license-verify-profile" profile in "mvn deploy site..." step. This is caused by extra artifacts in the build tree that the license verification plugin does not recognized. Examples of these artifacts are:

Eclipse control files, .classpath, .project
User created log files

Solution

Avoid the followings:

Don't use Eclipse's svn plugin to "Check out" files to a Eclipse project. Simply use the svn command, as described in the release instructions.
Don't create, directly or indirectly, any files under the release build tree.
Don't use the IBM JDK. By default, the IBM JDK will create heap dumps when hitting the OOM condition in some of our tests. These extra files throw off the rat:check processing. If you must use the IBM JDK, then also set MAVEN_OPTS=-Xdump:none.

Resources

Apache Apache Release FAQ
Signing Releases
Wendy's notes on Release Signing
Apache Mirroring Guidelines
Struts Release Instructions (upon which these instructions are based)

Change Notification Preferences

View Online | View Change | Add Comment

[CONF] OpenJPA > Releasing OpenJPA 1.2.x through 2.0.x