openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject [DISCUSS] Making a release
Date Sun, 12 Nov 2006 18:40:12 GMT
I'd like to propose something like this (edited the wiki page)

The main difference is that upon starting the release process, we  
create a branch in which to resolve the release issues while  
maintaining the trunk for further development.

h2. Tasks that need to be performed for each release

{info}In the examples below, it is assumed that the current committed  
version of OpenJPA is *0.9.6-incubating-SNAPSHOT*, and the version of  
the official release will be *0.9.6-incubating*{info}

# Make sure the [#One time setup] steps have been performed
# Create a branch from the trunk (or from a previous branch if  
maintaining a branch)
svn copy -m "Create branch for OpenJPA Release 0.9.6-incubating" 
# Change to the trunk for the next steps
# Update the pom.xml files to the subsequent version with the - 
SNAPSHOT suffix:
perl -pi -e "s;<version>0.9.6-incubating</version>;<version>0.9.7- 
incubating-SNAPSHOT</version>;g" pom.xml */pom.xml
# Commit the POM changes in the trunk
svn commit -m "Updated to version 0.9.7-incubating-SNAPSHOT"
# Change to the branch for the new release for the following steps
# Update the POMs to remove "-SNAPSHOT" from the version. If you have  
perl installed, you can easily do it with a single command:
perl -pi -e 's;<version>0.9.6-incubating-SNAPSHOT</ 
version>;<version>0.9.6-incubating</version>;g' pom.xml */pom.xml
# Commit the POM changes
svn commit -m "Updated to version 0.9.6-incubating"
# Perform the build with documentation and install it in the local  
repository (this step is required because there is a bug in Maven's  
javadoc generation aggregated between multiple modules):
mvn clean install -Pdocbook-profile,sign-release
{note}This operation will also sign the release artifacts with the  
*gpg* utility using the <username> key. If your code  
signing key is under a different address, specify it by appending the  
following argument to the command above: -{note}
# Verify the signatures:
gpg --multifile --verify openjpa-project/target/assembly/*.asc
# Build the javadocs and perform the deploy upload:
mvn verify deploy -Pjavadoc-profile,sign-release
# Start a vote for the release on the [mailto:open-jpa-] mailing list. For an example of the mail,  
see [this  archived vote| 
# If the vote is successful after 3 days, mail  
[] starting a vote for  
authorization to release
# Once that vote is successful, update the [ 
openjpa/downloads.html] page with information about the download
# Tag the view with the release number:
svn copy -m "OpenJPA Release 0.9.6-incubating" 
# The branch can now be used to apply patches for future releases  
using the branch as a basis (e.g. to create

Craig Russell
Architect, Sun Java Enterprise System
408 276-5638
P.S. A good JDO? O, Gasp!

View raw message