You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

The Tiles Project currently contains 3 releasable applications. Each of these should utilize the template below in order to perform the release. This will ensure that the releases are consistent, signed, and properly staged for voting. The 3 releasable modules include:

  1. Master Pom
  2. Framework (w/ Modules)
    1. tiles-api
    2. tiles-core
    3. tiles-test
  3. Showcase

Release Template

Preparing for the Release

#

Task

Completed

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

 

P3.

Setup new JIRA version level or update release on Roadmap

 

Test Build Distribution Checklist (A)

#

Task

Completed

A2.

$> mvn release:prepare

 

A3.

Validate that the release has been properly prepared. (TODO, this means POM Updated, Tag Created, etc. . .?)

 

A4.

$> mvn release:perform

 

A5.

Make sure that release:perform created sums, and uploaded to staging repo

 

A6.

Post testbuild announcement on dev@ lists

 

Vote (A)

#

Task

Completed

V1.

Send email to dev@ list announcing the vote. Copy private@

V2.

Wait until 5 days have passed (or the entire PMC has chimed in) and announce the results)

  • If release vote fails, including for a lack of quorum (3 binding +1s), remove from builds folder.
  • If a release vote passes (Alpha, Beta or GA), the release may be announced and mirrored, at the PMC's discretion.
  • If vote is GA, goto Checklist (C).

Vote Results

 

${PMC_MEMBER}

${GRADE}

Point Release Distribution Checklist (B)

#

Description

Completed

B1.

Update "Downloads" page on website and Test Downloads

 

Vote (B)

If initial vote is Alpha or Beta, voting can continue until a GA or "withdraw" vote passes, or there is a subsequent release.

#

Description

Completed

${PMC_MEMBER}

${GRADE}

General Availability Distribution Checklist (C)

Description

Completed

C1.

Copy Distribution to Mirrored Directories

 

C2.

After 24 hours, update "Downloads" page on website

 

C3.

Post an announcement to lists and website

 

Sample Test Build Announcement
Sample Release Quality Vote
Sample GA Build Announcement
One Time Setup Items (maven settings.xml, etc. . )

  • No labels