Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Release day - 1 week

Release day

Update the release notes

Add the release notes to distro/src/main/files/readme.html

Initial preparation in the codebase

  • Verify that the release notes have been added
  • Create the release branch: 
  • Update the version in the release branch: s/5.1-SNAPSHOT/5.1/g
  • Update the version in trunk to the next version's snapshot e.g. s/5.1-SNAPSHOT/5.2-SNAPSHOT/g
  • Update the version in trunk of module activiti-upgrade to the new snapshot.  e.g. s/5.1-ALWAYS-SNAPSHOT/5.2-ALWAYS-SNAPSHOT/g
  • Verification: Run the test suite: mvn -Pcheck clean install in the code base root

Generate the upgrade data

On your dev local machine, ensure that you have the upgrade properties to all the databases in ~/.activiti/upgrade/build.${database}.properties  Like for example:

  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/
  • ~/.activiti/upgrade/

Ensure that you have an up-to-date local git copy of the codebase

First ensure that you install the engine module with mvn clean install in the codebase root.

Then go to modules/activiti-upgrade and run

mvn -Pgenerate -Ddatabase=${database} clean package

That command produces the datafiles in activiti-upgrade/src/test/resources/org/activiti/db/${newVersion}/data.  If you do this before you branched the code, bear in mind that the directory name might contains the -SNAPSHOT.  Then you can just manually change the directory name of the version.

Run that generate profile for every database.

Then commit the resulting datafiles in git.  If this was done after branching the release, ensure that the commit is merged on master.

Test the distribution

  • Remove the 'skip.deploy.activiti.modeler=true' from $user.home/.activiti/
    Or even better: rename the temporary to e.g.
  • Verification: Run the demo setup in the root directory like this
  • That should eventually open up a couple of browser windows in which you can click around to see if everything works as expected

Upload the distribution

Build the distribution in directory distro:

Then upload the distro/target/ to

Upload the file to Amazon S3 (Through Ash/Panda/yourself)

Upload the activiti-modeler-5.x.war file to Amazon S3 (through Ash/Panda/yourself)

Publish the maven artifacts

Add following to ${user.home}/.m2/settings.xml

Note that this will save your password in plain text.
It is possible (since maven 2.1.0) to encrypt your password (untested):

Then do 

on the root of the sources. This will publish all artifact to the snapshot/release repo, depending whether '-SNAPSHOT' is added to the current project version.

snapshot repo:
release repo:

IMPORTANT: Due to a bug in Maven 2.2.0 and 2.2.1 see ( and, maven upload wrong checksums.

This is can currently only be fixed by logging in into the Alfresco Nexus app (, and manually selecting

the activiti folder, right-clicking and selecting 'rebuild Metadata'.

Publish the designer integration jar

To publish the designer integration jar, following command should be used

This requires you to have a ${user.home}/.m2/settings.xml specifying your credentials to upload release artifacts

Update the website

  • Publish the docs:  in directory distro
  • If they are updated, update the version andn publish the new .xsd schemas for and
  • Add the new release to the downloads page in the website
  • Commit the docs and download page updates to the website

Make noise

  • Blog and tweet about it
  • No labels