Project Retired
...
...
...
...
...
This
...
is
...
a
...
draft
...
to
...
document
...
changes
...
needed
...
from
...
the
...
first
...
release
...
plan.
...
No
...
2.0.1
...
is
...
imminent.
...
# | 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 | Released 2/06/07 | |
P3. | Setup new JIRA version level or update release on Roadmap |
| |
P4. | Mark the current JIRA version level as released |
|
# | Task | Instructions | Completed |
---|---|---|---|
A2. | | 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. | | After deployment, move the results from <repo>/ to <repo>/<version>/ | |
A5. | Make sure that release:perform created (md5 and sh1) and uploaded them to staging repo | ||
A6. | Post testbuild announcement on dev@ lists |
# | 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) |
Vote Results |
|
${PMC_MEMBER} | ${GRADE} |
# | Description | Completed |
---|---|---|
B1. | Update "Downloads" page on website and Test Downloads |
|
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} |
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 |
|