(tick) Tiles 2.0.x Release Plan

Tiles 2.0.x is targeted as a quality release.

Preparing for the Release

#

Task

Comments

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

 

 

P4.

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

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

 

 

Test Build Distribution Checklist (A)

#

Task

Instructions

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

 

 

Vote (A)

#

Task

Completed

V0.

Wait for comments from the test build announcement.

 

V1.

Send email to dev@ list announcing the vote.

 

V2.

Wait until 3 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

Count

Quality

+1

3

Alpha

+/-

0

 

-1

0

 

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

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

 

  • No labels