|
|
| (113 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.
| |
| # Release normal weeklies but with these changes in the master branch:
| |
| #* version.php: Move to $maturity = MATURITY_BETA and $release = 'X.Ybeta (Build:xxxxxxxx)'
| |
| #* tag git repo with: "vX.Y.0-beta"
| |
| #* Make packages available under download.moodle.org (and windows).
| |
| # Announce it?
| |
| # [[Weekly Code Review|Test / QA]] etc
| |
| # During the QA/Test weeks continuous integration will happen, releasing STABLE weeklies normally but master ones as often as possible (on demand).
| |
| # At some points we can be producing release candidates, they are normal builds but with:
| |
| #* version.php: Move to $maturity = MATURITY_RC and $release = 'X.YrcZ (Build:xxxxxxxx)'
| |
| #* tag git repo with: "vX.Y.0-rcZ"
| |
| #* Make packages available under download.moodle.org (and windows).
| |
| | |
| ==Stable release==
| |
| | |
| === 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.
| |
| #
| |
| #
| |
| #
| |
| # Update the Latest Release block on [http://moodle.org/news/ Moodle.org news]
| |
| # 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-29705 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).
| |
| | |
| ==== One week after ====
| |
| # Publish the X.Y+ packages @ download.moodle.org
| |
| # Create a new release notes page for the next version X.Y.1 (here you can find [[Release notes template|one template for that]])
| |
| # Prepare, spam and publish in Docs the security stuff ([http://moodle.org/security Security news] and [[:Category:Release notes|release notes]] with links to security advisories)
| |
| | |
| ==== One month after ====
| |
| # Publish the X.(Y+1)dev packages @ download.moodle.org
| |
| | |
| ==See also==
| |
| | |
| * [[Release process]]
| |
| | |
| [[Category:Processes|Release process]]
| |
| [[Category:Release notes|Release process]] | |
