Project Retired
The following checklist can be used for all releases. At tiles, we currently have three different artifacts to be releasedTiles 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:
...
# | Description | Completed | 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 A1. | Setup new JIRA version level or update release on Roadmap |
|
# | Description | Completed |
---|---|---|
A2. | |
|
A3. | Validate that the release has been properly prepared. (TODO, this means POM Updated, Tag Created, etc. . .?) |
|
A4. | |
|
A5. | Make sure that release:perform created sums, and uploaded to staging repo |
|
A6. | Post release-quality vote testbuild announcement on dev@ lists |
|
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) |
${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 |
|
Panel | ||
---|---|---|
| ||
Sample Test Build Announcement |