Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

(tick) Tiles 2.0.1 Release Plan

Tiles 2.0.1 is targeted as an alpha release.

...

#

Task

Instructions

Completed

A2.

$> mvn release:prepare;

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

(tick)

A3.

Validate the results of release:prepare

1) POM Updated 2) Tag Created)

(tick)

A4.

$> mvn release:perform

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

(tick)

A5.

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

 

(tick)

A6.

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

 

(tick)

A7.

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

 

(tick)

A6 A8.

Post testbuild announcement on dev@ lists

 

(tick)

...

#

Task

Completed

V0.

Wait for comments from the test build announcement.

(tick)

V1.

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

(tick)

V2.

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

(tick)

  • 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

 

${PMC_MEMBER}

${GRADE}

Point Release Distribution Checklist (B)

...

General Availability Distribution Checklist (C)

    Description

    Completed

    C0.

    Move maven artifacts to rsync repository

    (tick)

    C1.

    Copy Distribution to Mirrored Directories

     (tick)

    C2.

    After 24 hours, update "Downloads" page on website

     

    C3.

    Post an announcement to lists and website