Release procedure and checklist
From Joomla! Documentation
(Difference between revisions)
(New page: Category:Development) |
|||
| Line 1: | Line 1: | ||
| + | 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 == | ||
| + | |||
| + | 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 === | ||
| + | # 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 === | ||
| + | # 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 === | ||
| + | # 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 === | ||
| + | # 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 | ||
| + | # Update MD5 checksum information | ||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 18:56, 8 February 2008
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.
Contents |
Release checklist
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
- 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
- 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
- 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
- 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
- Update MD5 checksum information
