Tiles 2.0.0 Release

Due to a couple of NOTICE and Licensing issues, Tiles 2.0.0 has been deemed a test build.
See TILES-205, TILES-206, TILES-207, TILES-208, and TILES-209 for issues with the current release

Tiles 2.0.0 is targeted to be an alpha quality release.

Preparing for the Release

#

Task

Comments

Completed

P1.

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

 

(tick)

P2.

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

 

(tick)

P4.

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

Released 2/06/07

(tick)

P3.

Setup new JIRA version level or update release on Roadmap

 

(tick)

P4.

Mark the current JIRA version level as released

 

(tick)

Test Build Distribution Checklist (A)

#

Task

Completed

A2.

$> mvn release:prepare

(tick)

A3.

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

(tick)

A4.

$> mvn release:perform

(tick)

A5.

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

(tick)

A6.

Post testbuild announcement on dev@ lists

(tick)

Vote (A)

#

Task

Completed

V0.

Wait for comments regarding the test build.

(tick)

V1.

Send email to dev@ list announcing the vote.

(tick)

V2.

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

(thumbs down)

  • 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 (A)

  • Marked as Test Build due to issues with licenses and notices.

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

 

  • No labels