<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.
Once dev tools are released, go to the [OW2's MRM to promote|http://repository.ow2.org/nexus/index.html#stagingRepositories] the released artifacts into the repository containing released artifacts:
# Select the temporary repository containing artifacts just released,
# and "close" it,
# and "release" it.
h2. Releasing EasyCommons artifacts
{color:red}*TO BE DEFINED*{color}
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}
{warning}Caution, for *Debian package* and *ZIP distributions* artifacts, you must enter something as {{$\{petals-cli.version\}-1.1-SNAPSHOT}} as the new development version.{warning}
# 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"
{code}
Once Petals ESB projects are released, go to the [OW2's MRM to promote|http://repository.ow2.org/nexus/index.html#stagingRepositories] the released artifacts into the repository containing released artifacts:
# Select the temporary repository containing artifacts just released,
# and "close" it,
# and "release" it.
h1. After the release
h2. Acceptance & Integration tests
Update integration and acceptance tests against new SNAPSHOT versions.
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}
h2. Changelog
In [JIRA|http://jira.petalslink.com], release version of released projects. If needed, move unresolved issues to a next version or change its resolution state.
h2. 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'
h2. Communication
If needed, an announcement will be done on the right channels: Twitter, News on the Petals web-site, ...
E-mail
...