Release Management Process Description


The main aim of the release management process is to make sure the release cycle - from planning of a new version over its final release until the end of its lifecycle - follows a clear path and is visible to all parties involved including e.g. developers and end-users.

Therefore, the process is mainly a communication process, both internally within the team as well as externally to the users.

Initial and ongoing tasks

  • A page must be set up on which developers and users can always see upcoming dates and get a picture of the progress of the release (See e.g. the TYPO3 4.3 forge pages)
  • Clarify in the beginning of the release project what other infrastructure is needed, e.g. for team collaboration
  • Regularly inform the involved parties of the status, ideally by weekly or bi-weekly status reports published on the above mentioned central project location and the developer's mailing list

Tasks along the lifecycle of the release

Planning phase

Planning of the release is done by the core team and interested/committed parties of the community, not the release manager him/herself. The task of the release manager during the planning phase is guiding the process of defining what goes into the release and what doesn't, by e.g. guiding discussions in the core mailing list or leading the related workshops on the Developer Days (T3DD) into a productive direction as well as summing up the results subsequently.

Development phase / Alpha, Beta, RC releases

During the development phase, the release manager regularly checks the status of the subprojects, publishes dates of upcoming milestones and pre-releases (Alpha, Beta, RC).

Details on the policy regarding Alpha, Beta, RC versions can be found in the Core Team section on document.

Final release

[TODO: Write this section.]

See Wiki: Core Release Workflow.

Subsequent bugfix releases

The release manager remains responsible for the branch after the release, so he is the one to decide what goes into patch level releases of the version. The responsibility ends with the end of the branch's lifecycle.