h1. Requirements

# Internet connection
# You have an access to the OW2's MRM ([Nexus|http://repository.ow2.org/]), and your account can publish artifacts of the repository 'stagging'.
# Your Maven's setting file is right, containing:
#* MRM declarations,
#* Credential of the OW2's MRM to publish artifacts into the repository 'stagging'
{code}
<server>
<id>ow2.release</id>
<username>petals</username>
<password>......</password>
</server>
<server>
<id>ow2.snapshot</id>
<username>petals</username>
<password>......</password>
</server>
{code}
#* The secret GPG key to sign artifacts
{code}
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
{code}
{tip}If needed, import the secret key [{{secret.key}}|interne:Releaser un projet Petals^secret.key]: {{gpg --import secret.key}}{tip}
#* The credential of the GPG key:
{code}
<profile>
<id>gpg-passphrase</id>
<activation>
<property>
<name>performRelease</name>
<value>true</value>
</property>
</activation>
<properties>
<gpg.passphrase>.............</gpg.passphrase>
</properties>
</profile>

{code}

h1. Before release

Before to start the release process, disable the continuous integration to avoid failed build because of artifacts not promote from the repository 'stagging' to the repository 'public'.
In the [Jenkins console script|http://jenkins.petalslink.com/script], execute the following script to disable all jobs:
{code}
import hudson.model.*

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

h1. Releasing Petals ESB

To release Petals ESB, you will release, if needed, in the following order:
# Petals dev tools,
# Easycommons tools,
# Petals ESB.

h2. Releasing Petals dev tools

For each dev tools:
# prepare the release executing the command:
{code}
> mvn release:prepare
{code}
# perform the release executing the command:
{code}
> mvn release:perform
{code}

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

h2. Releasing EasyCommons artifacts

h2. Releasing Petals ESB artifacts

For the Petals root parent POM:
# prepare the release executing the command:
{code}
> mvn release:prepare -P prepare-release-profile
{code}
# perform the release executing the command:
{code}
> mvn release:perform -P perform-release-profile
{code}

For all other Petals ESB project:

# prepare the release executing the command:
{code}
> mvn release:prepare -Darguments="-P prepare-release-profile"
{code}
# perform the release executing the command:
{code}
> mvn release:perform -Darguments="-P perform-release-profile"

h2. Enable Jenkins's jobs

Now, the continuous integration can be re-enable. In the [Jenkins console script|http://jenkins.petalslink.com/script], execute the following script to enable all jobs:
{code}
import hudson.model.*

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

h1. Release the documentation

If the released component has a documentation, copy the documentation 'SNAPSHOT' renaming 'SNAPSHOT' by the right version.

h1. Communication

If needed, an announcment will be done on the right channels: Twitter, News on the Petals web-site, ...