Page History

P1.

Announce your intentions to start the release process on the developer mailing list.

P2.

Copy this release plan template in order to create a release plan for the specific version being released

P4.

Ensure that the current version of tiles-master has been released

Released 2/06/07 v1 Released 2007-02-06

P3.

Setup new JIRA version level or update release on Roadmap

P4.

Mark the current JIRA version level as released

Completed

A2.

$> mvn release:prepare -P release;

When prompted use tiles-2.x.x as your version, do not accept the default

A3.

Validate the results of release:prepare

1) POM Updated 2) Tag Created)

A4.

$> mvn release:perform -P release

After deployment, move the results from <repo>/ to <repo>/<version>/

A5.

Make sure that release:perform created (md5, sha1, and asc) and uploaded them to staging repo

A6.

Checkout the tag and execute 'mvn clean site install -P release'

A7.

Post the resulting assemblies to <repo>/<version>/

A8.

Post testbuild announcement on dev@ lists

C0.

Move maven artifacts to rsync repository

C1.

Copy Distribution to Mirrored Directories

C2.

After 24 hours, update "Downloads" page on website

C3.

Post an announcement to lists and website