Difference between revisions of "Release procedure and checklist"
From Joomla! Documentation
AmyStephen (talk | contribs) |
AmyStephen (talk | contribs) |
||
Line 59: | Line 59: | ||
#* [http://www.joomla.org/content/category/5/39/95/ MD5 Sums] | #* [http://www.joomla.org/content/category/5/39/95/ MD5 Sums] | ||
− | === Calculating | + | === Calculating Release Statistics === |
# Extract *all* issues from Tracker into spreadsheet. Make note of the date of the last release and the number of active issues at the time of the last release. | # Extract *all* issues from Tracker into spreadsheet. Make note of the date of the last release and the number of active issues at the time of the last release. |
Revision as of 23:01, 1 June 2009
There is a general checklist when a version of Joomla! is released. Keep in mind that a major release differs a lot from a Minor Release or even a Maintenance Release. The checklist here describes the steps that need to be done for (at least) Maintenance Release and Minor Release.
Release checklist[edit]
It depends on the Development Cycle when the checklist is triggered. A release can be done during every stage of the Development Cycle, it does not matter if you release a beta or a stable version, this is a general checklist that can be used when releasing a new version of Joomla! The checklist starts when it's decided to release a version:
Preparation phase[edit]
- Communication pre-release: check with all Working Group Coordinators for status
- Communication pre-release: check with Lead Developers for status
- Communication pre-release: inform Bug Squad and Development Team of upcoming release
- Decision: when the above has positive result, set a date and time for release
- Communication pre-release: inform Global Moderators about upcoming release
- Communication pre-release: check availability and assign release tasks to Core and work-group members.
- Close trunk on predefined date and time (Development Coordinator, also sends an e-mail to development list).
- Image for front page download module, has to be modified for the release.
- Contact foundation work group for creation of Front page announcement.
- Determine release name
Pre-execution phase[edit]
- Apply latest translations (need to be delivered by translation work group).
- Create test package.
- Offer test package to testers: Bug Squad members, Development Team members, translation members
- If problems are found during this stage, go back to fix the problem. Use the Joomla! Maintenance Procedures and repeat until tests are performed successfully.
Execution phase[edit]
- Change version information.
- Enable install check.
- Add entry in CHANGELOG.php file
- Package build.
- Offer test package to testers: Bug Squad members, Development Team members, translation members
- If problems are found during this stage, go back to fix the problem. Use the Joomla! Maintenance Procedures and repeat until tests are performed successfully.
- Add package to joomlacode.org
- Publish announcement on joomla.org and the forum, change download module image and link
- Make static copy of front page with announcement to be used if server load becomes critical.
Finalization phase[edit]
- Tag SVN.
- Un-freeze the trunk, send e-mail to work groups and mailing lists (Development Team and Bug Squad).
- Undo install check.
- Change content on joomla.org and dev.joomla.org (see pages to update)
- Update MD5 checksum information
- Update nightly builds to reflect new release
Pages to update[edit]
- Global:
- 1.5:
- Create new Wiki article called 'Category:Version 1.5.X FAQ'. Add an overall note for the release in the body of the article using the previous version as a Guide. Insert the following into the article: [[Category:Version 1.5 FAQ]]. Include a link to the 'Category:Version 1.5.x FAQ' page in the Release notes.
- Update Version History
- Update Joomla! Codenames
- 1.0:
Calculating Release Statistics[edit]
- Extract *all* issues from Tracker into spreadsheet. Make note of the date of the last release and the number of active issues at the time of the last release.
- Set a filter on the "Closed Date" column to be "after" "the day of the last release".
- Calculate "Closed" count by aggregating status values for Closed, Duplicate Report, Known Issue, Not a bug, Not Joomla! Core, Unable to Confirm.
- Calculate "Fixed in SVN" count by aggregating status values for Open and Information Required. (Note: this value is presented two times in the report.)
- Set a filter on the "Closed Date" column to be blanks:
- Calculate "Open" count by aggregating status values for "Open" and "Information Required."
- Calculate "Confirmed" count by aggregating status values for "Confirmed" and "In Progress."
- Calculate "Pending" count by aggregating status values for "Pending" and "Ready to Commit."
- Calculate the "New Active Issues" by aggregating the "Open", "Confirmed" and "Pending" counts.
- Calculate the "net increase/decrease" by subtracting the "Last Release Active Issues" from the "New Active Issues."
- Count the "number of commits" by reviewing the CHANGELOG.php file and counting the documented commits.