Requirements

1. Internet connection
2. You have an access to the OW2's MRM (Nexus), and your account can publish artifacts of the repository 'stagging'.
3. Your Maven's setting file is right, containing:
   • MRM declarations,
   • Credential of the OW2's MRM to publish artifacts into the repository 'stagging'

         <server>
           <id>ow2.release</id>
           <username>petals</username>
           <password>......</password>
         </server>
         <server>
           <id>ow2.snapshot</id>
           <username>petals</username>
           <password>......</password>
         </server>
     

   • The secret GPG key to sign artifacts

     cdeneux@cdeneux-laptop:~$ gpg --list-secret-keys
     /home/cdeneux/.gnupg/secring.gpg
     --------------------------------
     sec   2048R/09334662 2012-10-08
     uid                  Petals (ESB) <petals-dev@ow2.org>
     ssb   2048R/C8353498 2012-10-08
     

     If needed, import the secret key secret.key: gpg --import secret.key

   • The credential of the GPG key:

       <profile>
          <id>gpg-passphrase</id>
          <activation>
           <property>
             <name>performRelease</name>
             <value>true</value>
            </property>
          </activation>
          <properties>
            <gpg.passphrase>.............</gpg.passphrase>
          </properties>
        </profile>
     

Before release

Before to start the release process, disable the continuous integration to avoid failed builds because of artifacts not promoted from the repository 'stagging' to the repository 'public'.
Deactivating Jenkins jobs can be done manually through the Jenkins UI or using a script as following executed in the Jenkins console script:

import hudson.model.*

// For each project
for(item in Hudson.instance.items) {
  println("JOB : "+item.name)
  item.disabled=true
  item.save()
  println("\n=======\n")
}

Catution to deactivate only Jenkins jobs associated to the projects that will be released !

Releasing Petals ESB

To release Petals ESB, you will release, if needed, in the following order:

1. Petals dev tools,
2. Easycommons tools,
3. Petals ESB.

Releasing Petals dev tools

For each dev tools:

1. prepare the release executing the command:

   > mvn release:prepare
   

2. perform the release executing the command:

   > mvn release:perform
   

During the perform phase, Maven will ask you the PGP's pass-phrase.

Once dev tools are released, go to the OW2's MRM to promote the released artifacts into the repository containing released artifacts:

1. Select the temporary repository containing artifacts just released,
2. and "close" it,
3. and "release" it.

Releasing EasyCommons artifacts

Releasing EasyCommons artifacts for branchs 4.x.y

First, prepare the release executing the command:

> mvn release:prepare -DtagBase=https://svn.petalslink.org/svnroot/tags

Next, perform the release executing the command:

> mvn release:perform

Releasing EasyCommons artifacts for trunk

Same as releasing Petals ESB artifacts of trunk.

Releasing Petals ESB artifacts

Releasing Petals ESB artifacts for branchs 4.x.y

For the Petals root parent POM:

1. First, prepare the release executing the command:

   > mvn release:prepare -P prepare-release-profile -DtagBase=https://svn.petalslink.org/svnroot/tags
   

2. Next, perform the release executing the command:

   > mvn release:perform -P perform-release-profile
   

For all other Petals ESB projects:

1. First, prepare the release executing the command:

   > mvn release:prepare -Darguments="-P prepare-release-profile" -DtagBase=https://svn.petalslink.org/svnroot/tags
   

2. Next, perform the release executing the command:

   > mvn release:perform -Darguments="-P perform-release-profile"
   

Once Petals ESB projects are released, go to the OW2's MRM to promote the released artifacts into the repository containing released artifacts:

1. Select the temporary repository containing artifacts just released,
2. and "close" it,
3. and "release" it.

Releasing Petals ESB artifacts for trunk

For the Petals root parent POM:

1. prepare the release executing the command:

   > mvn release:prepare -P prepare-release-profile
   

2. perform the release executing the command:

   > mvn release:perform -P perform-release-profile
   

For all other Petals ESB projects:

1. prepare the release executing the command:

   > mvn release:prepare -Darguments="-P prepare-release-profile"
   

   Caution, for Debian package and ZIP distributions artifacts, you must enter something as ${petals-cli.version}-1.1-SNAPSHOT as the new development version.

   Preparing release from a branch as .../svnroot/branches-legacy/petals-esb-enterprise-4.2.x requires the definition of the right tag base adding the following argument to the previous command line: -DtagBase=https://svn.petalslink.org/svnroot/tags

   The profile prepare-release-profile is required to disable the check about SCM URL. During the release preparation, SCM URL are updated just before to tag the artifact and the SCM URL declared in the POM will not match the current SCM URL, so SCM enforcer rule must be disable.

2. perform the release executing the command:

   > mvn release:perform -Darguments="-P perform-release-profile"
   

   The profile perform-release-profile is required to sign all deployed artifacts (required by OW2).

Once Petals ESB projects are released, go to the OW2's MRM to promote the released artifacts into the repository containing released artifacts:

1. Select the temporary repository containing artifacts just released,
2. and "close" it,
3. and "release" it.

After the release

Acceptance & Integration tests

Update integration and acceptance tests against new RELEASE and SNAPSHOT versions.

Enable Jenkins's jobs

Now, the continuous integration can be re-enable, manually or executing a script as following in the Jenkins console script:

import hudson.model.*

// For each project
for(item in Hudson.instance.items) {
  println("JOB : "+item.name)
  item.disabled=false
  item.save()
  println("\n=======\n")
}

Caution to re-activate only Jenkins jobs that you have deactivated previously !

Changelog

In JIRA, release version of released projects. If needed, move unresolved issues to a next version or change its resolution state.

Release the documentation

If the released component has a documentation, release the documentation 'SNAPSHOT' renaming 'SNAPSHOT' by the right version, next copying the released documentation with a new name ending with 'SNAPSHOT'

The component having a documentation to release are:

• Petals ESB container,
• Petals JBI components,
• Petals CLI,
• Petals Ant Tasks,
• Maven Petals Plugin

Communication

Announcements must be done on the right channels: on Twitter and in section 'News' of the Petals web-site, ...

Update the Petals ESB web-site

To update the Petals ESB web-site:

1. Clone the Git repository https://github.com/petalslink/petals.ow2.org,
2. Add a file download-petals-X.Y.Z.md for the new version. It's content is similar to other files download-petals-X.Y.Z.md,
3. Adjust the content of download.md,
4. Commit and push changes to the Git repository,
5. A Jenkins job is automatically launch to deploy the Petals ESB web-site on the web-site stagging area of the OW2 forge
6. Publish the Petals web-site through the OW2 forge:
   1. Go to http://forge.ow2.org,
   2. Sign in as manager (petals/xxxxx),
   3. Go to http://forge.ow2.org/project/admin/?group_id=213,
   4. Push on the button Push Project Web Site from Development to Production Now (scroll down the web page to see the button),
   5. Check the Petals ESB web site going to http://petals.ow2.org/download.html, and checking the content of its links.

Twitter

You can use your personal account to publish an announcement of the new release on Twitter.
Announcement sample:

@linagora The new maintenance release 4.2.2 of @petalsesb is out: http://petals.ow2.org/download-petals-4.2.4.html

All tweets done with a personal account should be retweeted with the account 'petalslink' to be automatically listed on the home page of the Petals web site (see [consulting:Le Compte Twitter de Petals ESB] for more information on account 'petalslink').