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 17 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

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: ant test.demo.setup in directory qa

Upload the distribution

Build the distribution in directory distro:

Then upload the distro/target/ to

Trigger Ash to upload the file to Amazon S3

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

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns=""

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