|
|
| (121 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| {{Template:Work_in_progress}}
| | #REDIRECT [[Release process]] |
| | |
| This page describes the standard procedures for making a major release e.g. Moodle 2.0.
| |
| | |
| ==Beta release==
| |
| | |
| One month before:
| |
| # Freeze stable development and post in the [http://moodle.org/mod/forum/view.php?id=55 General developer forum] to inform everyone of the freeze | |
| # Review and complete the [[Releases|release notes]] of the upcoming version.
| |
| # [[Weekly Code Review|Test / QA]] etc
| |
| | |
| | |
| Release day:
| |
| | |
| # Verify all unit tests, QAs and integration tests pass!
| |
| # Run the [https://github.com/skodak/mdlrelease/blob/master/weeklybuild.txt mdlrelease] process (with the special steps for Major releases).
| |
| #
| |
| # In Tracker, "release" the current version (with current date) and push any remaining open issues to the next point release (eg 2.1 -> 2.1.1) for developers to deal with there.
| |
| #
| |
| #
| |
| #
| |
| # Post about the release in the [http://moodle.org/news/ moodle.org news]
| |
| | |
| Post release:
| |
| | |
| # Clone MDL-28169 and MDL-28170, to be resolved ASAP.
| |
| # Clone MDL-20840 and MDL-20722 for next minor release X.Y.1 handling of security issues / security advisories.
| |
| # Prepare and publish the calendar for next Major release (basis are, for 6-months periods: 1 month for furious bugfixing release, 1 month for planning, 3 months for developments, 1 month for QA, candidates/betas/release).
| |
| # 1 week after release, publish the X.Y+ packages @ download.moodle.org
| |
| # 1 month after release, when next dev starts to diverge, publish the X.(Y+1)dev packages @ download.moodle.org
| |
| | |
| ==See also==
| |
| | |
| * [[Release process]]
| |
| | |
| [[Category:Processes|Release process]]
| |
| [[Category:Release notes|Release process]] | |
