Child pages
  • Sakai CLE release guide (pre 2.9)
Skip to end of metadata
Go to start of metadata

Create a release branch

Current practice dictates that non-indie *.x branch pom versions must remain constant for the life of the branch. *.x branch pom files are versioned major version.minor version-SNAPSHOT (e.g., 2.8-SNAPSHOT). In addition, no snapshot jars are permitted in the Maven2 release repo. Because of these rules, particularly the latter, a release branch must be created prior to a release for each non-indie project in order to reset each pom <version> to a non-snapshot version (e.g., 2.8.1).

Release branches should only be created after all *.x branch blockers have been eliminated. Once the release branch is created the *.x branch is free to accept merged code not intended for the release. However, given the vagaries of CLE quality assurance late breaking release blockers are often discovered after the release branch is created. This creates challenges for the release team and branch managers since blocker fixes must be merged both to the *.x maintenance branch AND the release branch. Great vigilance is required to track the commit stream to ensure that fixes required for the release are not missed.

Indie projects, which leverage the Maven release plugin, are easier to manage. Releases are performed from existing *.x maintenance branches (no release branch is required) and the plugin handles pom version changes, tag creation and binaries generation and deployment automatically.

Non-indie release branches (as well as tags) are created using the following bash script.


The script takes six arguments.

$ bash sakaitagbuilder-2.8.bash [Jira ticket number] \
[source branch] \ 
[take HEAD=true|false] \
[target=branches|tags] \
[sakai version] \
[version suffix=mXX|aXX|bXX|rcXX]

$ bash sakaitagbuilder-2.8.bash SAK-20967 sakai-2.8.x true branches 2.8.1

Update pom.xml <version>, master pom.xml <properties>,

1. Update <version>; find/replace 2.*-SNAPSHOT with release version
<version>2.8-SNAPSHOT</version> -> <version>2.8.1</version> 
2. Update <sakai.version> (master pom.xml)
3. Update Indie version <properties> (master pom.xml)
 . . .
4. Review other properties such as Tomcat or Quartz versions and update as necessary.
5. Update
6. Check stealth settings and adjust accordingly for the default and demo
# A stealth tool is a tool that is running in Sakai but is not available to be added to a site in Worksite Setup.
# For Development/QA purposes stealthTools property will be commented out; release artifacts will have the property uncommented.
# STEALTH TOOLS.  A stealth tool is a tool that is running in Sakai, but is not available to be added to a site in Worksite Setup.

(minus) Review reference/docs/ version.service and version.sakai. These files should not have been updated by developers. Check logs for changes.


Double check /reference/docs/conversion

(warning) Review sql conversion scripts, update and commit as necessary.

/master/pom.xml: confirm <distributionManagement>, maven-taglib-plugin and Sakai maven plugin settings. Commit changes if necessary.
1. <distributionManagement>
      <name>Local Test</name>
      <name>Local Test</name>

(warning) Consider deploying directly to Maven2 release repo. See rationale below.

            <name>Sakai snapshot Repo</name>
            <name>Sakai maven2 repository</name>
            <name>Sakai release Site</name>
2. maven-taglib-plugin
		<!-- <taglib.src.dir>src/webapp/WEB-INF</taglib.src.dir> -->
3. Confirm sakai maven plugin <version> equals 1.2.0
    . . . .
4. Disable snapshot repo

(tick) Insulate deployers against the possibility of snapshots leaking into release.

. . .
            <name>Sakai Maven Repo</name>
. . .
Base pom.xml: confirm javadoc plugin definition. Beware setting max memory settings too low.
                    <additionalJOption>-J-Xms168m -J-Xmx1024m -J-XX:PermSize=128m -J-XX:NewSize=64m</additionalJOption>

Check out, install, deploy and start up the release branch in Tomcat.

Perform a test build of the release branch.

Local environment set up

  1. Delete .m2/repository/org/sakaiproject (force fresh install)
  2. Create new MySQL 5.1.x database named "sakai"
  3. Start with clean Tomcat 5.5.33 servlet container
  4. Confirm maven-taglib is defined in .m2/settings.xml
<!-- Reference plugins in order to use <goalPrefix> short-hand -->
svn co 2.8.1
cd 2.8.1
mvn clean install sakai:deploy

If build fails, debug. If build is successful, start Tomcat. Check logs for warnings and errors.

Build and deploy release binaries to Sakai Maven2 release repo.

(minus) Warn: create backup folder of /var/www/html/maven2/org/sakaiproject on before deploying release binaries to repo.

Get copy of maven2/org/sakaiproject repo

Tar up maven2/org/sakaiproject and sftp or scp across the network to build machine and deploy binaries locally. This step is now prohibitively expensive in terms of download time.

(warning) Consider eliminating this step and instead adjust build script to deploy non-indie projects directly to the repo via scp.

The challenge here is that you need all the Maven metadata files locally so that they can be properly updated during the release.

Run sakai-cle-artifactmaker.bash

Script generates demo, bin and src tar/zip artifacts and then deploys release binaries to "local" repo updating Maven metadata files along the way.


$ bash sakai-cle-artifactmaker.bash [release version] [Source path]

$ bash sakai-cle-artifactmaker.bash 2.8.1 /Users/arwhyte/Development/svn/sakai/branches/2.8.1

Download samigo audio jar from Maven2 release repo and verify that jar is signed.

jarsigner -verify sakai-samigo-audio-2.8.1.jar

Check demo, bin and src artifacts

Update Sakai Maven2 repo

Transfer mavenrepo-2.8.1.tgz to

(warning). Ensure backup copy of /var/www/html/maven2/org/sakaiproject exists. Then untar updated files:

sudo tar -xvzf mavenrepo-2.8.1.tgz -C /var/www/html/

Cut release tag from 2.8.1 branch

The sakaitagbuilder.bash script accepts two arguments: Sakai version and tag suffix (e.g., blank, beta01, rc01, qa01). In this case no tag suffix is required.

bash sakaitagbuilder-2.8.bash [JIRA ISSUE] sakai-2.8.1 tags 2.8.1

After the release is generated, backup .m2/repository/org/sakaiproject, whack original (to ensure someone new can populate their repo from scratch), download the release tag and build and deploy it to a fresh Tomcat and fresh MySQL database.

Update Jira

Visit the SAK project and release sakai-2.8.1. Move all open Jiras to next (tentative) version.

Update release documentation

Ideally this work should already be completed. But in case it's not update the following pages:

1. Release page:
2. Confluence release documentation: