Major release process: Difference between revisions
From MoodleDocs
m (→Release day) |
m (→Release day) |
||
Line 49: | Line 49: | ||
# Update links on [[Releases]] page | # Update links on [[Releases]] page | ||
# In Tracker, "release" the current version (with current date) and push any remaining open issues to the next point release (eg 2.2 -> 2.2.1) for developers to deal with there. his must be done both for the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011 Moodle Project] and the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033 Non-core contributed modules project]. | # In Tracker, "release" the current version (with current date) and push any remaining open issues to the next point release (eg 2.2 -> 2.2.1) for developers to deal with there. his must be done both for the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011 Moodle Project] and the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033 Non-core contributed modules project]. | ||
# In Tracker, create the new "Pull X.Y Branch" and "Pull X.Y Diff URL" custom fields and spread them to all the screens requiring them. | |||
# Update the Latest Release block on [http://moodle.org/news/ Moodle.org news] | # 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 about the release in the [http://moodle.org/news/ moodle.org news] |
Revision as of 22:48, 8 December 2011
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
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 General developer forum to inform everyone of the freeze
- Review and complete the release notes and upgrading 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" (and MOODLE_XY_BETA as description and CVS tag)
- Make packages available under download.moodle.org (and windows).
- Announce it in forums (ideally once packages are available).
- Test / QA, etc
- Review all the issues with labels "docs_required" and "qa_test_required", cleaning while done.
- 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 (Z = 1, 2, 3..), 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" (and MOODLE_XY_RCZ as description and CVS tag)
- Make packages available under download.moodle.org (and windows).
One week before
- Clone as many filters as needed in the Tracker, modifying them to point to the new, upcoming, branch (keeping same perms, title...).
- Create new minor version X.Y.1 in the Tracker.
- To decide: Bump all versions and requires along all plugins in codebase to current date.
Stable release
Release day
- Verify all unit tests, QAs and integration tests pass!
- Run the mdlrelease process (with the special steps for Major releases).
- In the download server:
- Create the stableXY and download/stableXY dirs
- cvs -q update -dP all code on download server
- Edit /opt/bin/moodle-cvsupdate and /opt/bin/moodle with new version
- Create and run moodle-makenightlystableXY (add it where necessary - crons and friends)
- Go to download/stableXY
- Copy current daily as release package:
- cp moodle-latest-XY.zip moodle-X.Y.zip
- cp moodle-latest-XY.tgz moodle-X.Y.tgz
- Edit download index.php page with new release info and links
- Create new windows packager script (cloning the current master one and configuring it) and add it where necessary - cron scripts and friends)
- Run moodle-makewindowspackages so all the windows packages will be rebuilt
- Edit download windows/index.php page with new release info (always keeping the "+")
- Run SF's mirror script
- Update links on Releases page
- In Tracker, "release" the current version (with current date) and push any remaining open issues to the next point release (eg 2.2 -> 2.2.1) for developers to deal with there. his must be done both for the Moodle Project and the Non-core contributed modules project.
- In Tracker, create the new "Pull X.Y Branch" and "Pull X.Y Diff URL" custom fields and spread them to all the screens requiring them.
- Update the Latest Release block on Moodle.org news
- Post about the release in the moodle.org news
Post release
- Clone MDL-30604 and MDL-30605, 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 one template for that)
- Prepare, spam and publish in Docs the security stuff (Security news and release notes with links to security advisories)
One month after
- Publish the X.(Y+1)dev packages @ download.moodle.org