Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<h1>Release day - 1 week</h1><ul><li>Code freeze. Ask on the dev forum who has outstanding work and synchronize on creating the release branch.</li></ul><h1>Release day</h1><h3><span style="color: rgb(0,51,102);"><strong>Update the release notes</strong></span></h3><p>Add the release notes to distro/src/main/files/readme.html</p><h3>Initial preparation in the codebase</h3><ul><li>Verify that the release notes have been added</li><li>Create the release branch: </li></ul><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>svn -m "creating release branch for 5.11" copy https://svn.activiti.org/repo/activiti/trunk https://svn.activiti.org/repo/activiti/tags/activiti-5.11 </pre></td></tr></table><ul><li>Update the version in the release branch: s/5.1-SNAPSHOT/5.1/g</li><li>Update the version in trunk to the next version's snapshot e.g. s/5.1-SNAPSHOT/5.2-SNAPSHOT/g</li><li>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</li><li>Verification: Run the test suite: mvn -Pcheck clean install in the code base root</li></ul><h3>Generate the upgrade data</h3><p>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:</p><ul><li><pre>~/.activiti/upgrade/build.db2.properties</pre></li><li><pre>~/.activiti/upgrade/build.h2.properties</pre></li><li><pre>~/.activiti/upgrade/build.mssql.properties</pre></li><li><pre>~/.activiti/upgrade/build.mysql.properties</pre></li><li><pre>~/.activiti/upgrade/build.oracle.properties</pre></li><li><pre>~/.activiti/upgrade/build.postgres.properties</pre></li></ul><p>Ensure that you have an up-to-date local git copy of the codebase</p><p>First ensure that you install the engine module with mvn clean install in the codebase root.</p><p>Then go to modules/activiti-upgrade and run</p><p>mvn -Pgenerate -Ddatabase=postgres -Dmaven.test.skip=true clean package</p><p>That command produces the datafiles in activiti-upgrade/src/test/resources/org/activiti/db/${project.version}/data.  Bear in mind that the default directory name is based on the project version, which might contain the -SNAPSHOT.  Then you can just manually change the directory name of the version.</p><p>If you want to produce new data files for older versions, use the upgradeVersion property like this</p><p>mvn -Pgenerate -Ddatabase=postgres -DupgradeVersion=5.8 -Dmaven.test.skip=true clean package</p><p>Run that generate profile for every database.</p><p>Then commit the resulting datafiles in git.  If this was done after branching the release, ensure that the commit is merged on master.</p><h3>Test the distribution</h3><ul><li>Remove the 'skip.deploy.activiti.modeler=true' from $user.home/.activiti/build.properties<br /> Or even better: rename the build.properties temporary to e.g. XXXbuild.properties</li><li>Verification: Run the demo setup in the root directory like this</li></ul><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>ant -f qa/build.xml test.demo.start 
</pre></td></tr></table><ul><li>That should eventually open up a couple of browser windows in which you can click around to see if everything works as expected</li></ul><h3>Upload the distribution</h3><p>Build the distribution in directory distro:</p><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>ant clean distro
</pre></td></tr></table><p>Then upload the distro/target/activiti-5.11.zip to <a href="http://ts.alfresco.com/share/page/site/activiti/documentlibrary#path=/Downloads&amp;page=1">http://ts.alfresco.com/share/page/site/activiti/documentlibrary#path=/Downloads&amp;page=1</a></p><h3>Publish the maven artifacts</h3><p><span style="color: rgb(0,0,0);">Add following to ${user.home}/.m2/settings.xml</span></p><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>&lt;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">
  &lt;servers>
    &lt;server>
      &lt;id>alfresco.snapshot.repo&lt;/id>
      &lt;username>jbarrez&lt;/username>
      &lt;password>XXX&lt;/password>
    &lt;/server>
    &lt;server>
      &lt;id>alfresco.release.repo&lt;/id>
      &lt;username>jbarrez&lt;/username>
      &lt;password>XXX&lt;/password>
    &lt;/server>
  &lt;/servers>
&lt;/settings>
</pre></td></tr></table><p><span style="color: rgb(0,0,0);">Note that this will save your password in plain text.</span><br /> <span style="color: rgb(0,0,0);">It is possible (since maven 2.1.0) to encrypt your password (untested): </span><a href="http://maven.apache.org/guides/mini/guide-encryption.html">http://maven.apache.org/guides/mini/guide-encryption.html</a></p><p>Then do </p><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>mvn -Pdeploy clean deploy
</pre></td></tr></table><p><span style="color: rgb(0,0,0);">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.</span></p><p><span style="color: rgb(0,0,0);">snapshot repo: </span><a href="http://maven.alfresco.com/nexus/content/repositories/activiti-snapshots/">http://maven.alfresco.com/nexus/content/repositories/activiti-snapshots/</a><br /> <span style="color: rgb(0,0,0);">release repo:</span> <a href="http://maven.alfresco.com/nexus/content/repositories/activiti/">http://maven.alfresco.com/nexus/content/repositories/activiti/</a></p><p><strong>IMPORTANT:</strong> Due to a bug in Maven 2.2.0 and 2.2.1 see (<a href="http://jira.codehaus.org/browse/MNG-4235">http://jira.codehaus.org/browse/MNG-4235</a> and <a href="http://jira.codehaus.org/browse/MNG-4301">http://jira.codehaus.org/browse/MNG-4301</a>), maven upload wrong checksums.</p><p>This is can currently only be fixed by logging in into the Alfresco Nexus app (<a href="http://maven.alfresco.com/nexus/index.html#welcome">http://maven.alfresco.com/nexus/index.html#welcome</a>), and manually selecting</p><p>the activiti folder, right-clicking and selecting '<em>rebuild Metadata</em>'.</p><h3>Update the website</h3><ul><li>Publish the docs:  in directory distro</li></ul><table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>ant publish.docs
</pre></td></tr></table><ul><li>If they are updated, update the version andn publish the new .xsd schemas for <a href="http://activiti.org/cfg">http://activiti.org/cfg</a> and <a href="http://activiti.org/bpmn">http://activiti.org/bpmn</a></li><li>Add the new release to the downloads page in the website</li><li>Commit the docs and download page updates to the website</li></ul><h3>Make noise</h3><ul><li>Blog and tweet about it</li></ul>