Development:Release process - Revision history

Stronk7: /* For a stable release on an existing branch XX with point value Y */

2011-05-06T14:19:39Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 14:19, 6 May 2011
Line 12:		Line 12:
	# Make sure all the Unit tests pass!		# Make sure all the Unit tests pass!
	# Edit version.php, update name and version to new point release and commit in the integration repository		# Edit version.php, update name and version to new point release and commit in the integration repository
	# Tag the integration repository with a tag name vX.Y.Z using "MOODLE_XXY" as a tag message		# Run the [https://github.com/skodak/mdlrelease/blob/master/weeklybuild.txt mdlrelease] process, that will do, for a release:
	# push change to main git repo, github and Gitorious		#* Tag the integration repository with a tag name vX.Y.Z using "MOODLE_XXY" as a tag message
	# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)		#* push change to main git repo, github and Gitorious
	# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release		#* sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)
	# ~~'''cvs tag -FR vX.X.Y''' to tag everything in the release~~		#* '''cvs tag -FR MOODLE_XXY''' to tag everything in the release
	# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release		#* '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release
	# '''cvs -q update -dP''' all code on download server		# '''cvs -q update -dP''' all code on download server
	# Run moodle-makenightlystableXX		# Run moodle-makenightlystableXX

Stronk7: Clarifying git tagging

2011-05-06T13:09:46Z

Clarifying git tagging

← Older revision		Revision as of 13:09, 6 May 2011
Line 12:		Line 12:
	# Make sure all the Unit tests pass!		# Make sure all the Unit tests pass!
	# Edit version.php, update name and version to new point release and commit in the integration repository		# Edit version.php, update name and version to new point release and commit in the integration repository
	# Tag the integration repository with ~~MOODLE_XXY (old style) '''and'''~~ vX.X.~~Y (new style)~~		# Tag the integration repository with a tag name vX.Y.Z using "MOODLE_XXY" as a tag message
	# push change to main git repo, github and Gitorious		# push change to main git repo, github and Gitorious
	# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)		# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)
Line 35:		Line 35:
	# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).
	# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).
	~~# final step - tag the release in git repositories (integration, main and mirrors) - to be done by Martin Dougiamas~~

	One week later:		One week later:

Stronk7: /* For a stable release on an existing branch XX with point value Y */

2011-02-14T09:56:44Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 09:56, 14 February 2011
Line 9:		Line 9:
	# [[Development:Weekly Code Review\|Test / QA]] etc		# [[Development:Weekly Code Review\|Test / QA]] etc

	Release day:		Release day: (exactly before the next integration cycle begins on Monday)
	# Make sure all the Unit tests pass!		# Make sure all the Unit tests pass!
	# Edit version.php, update name and version to new point release and commit in the integration repository		# Edit version.php, update name and version to new point release and commit in the integration repository

Dougiamas: /* For a stable release on an existing branch XX with point value Y */

2011-02-14T09:35:33Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 09:35, 14 February 2011
Line 12:		Line 12:
	# Make sure all the Unit tests pass!		# Make sure all the Unit tests pass!
	# Edit version.php, update name and version to new point release and commit in the integration repository		# Edit version.php, update name and version to new point release and commit in the integration repository
			# Tag the integration repository with MOODLE_XXY (old style) '''and''' vX.X.Y (new style)
	# push change to main git repo, github and Gitorious		# push change to main git repo, github and Gitorious
	# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)		# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)
	# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release		# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release
			# '''cvs tag -FR vX.X.Y''' to tag everything in the release
	# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release		# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release
	# '''cvs -q update -dP''' all code on download server		# '''cvs -q update -dP''' all code on download server

Stronk7: /* For a stable release on an existing branch XX with point value Y */

2010-12-25T23:43:33Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 23:43, 25 December 2010
Line 29:		Line 29:
	# Update the [[Latest release notes]] page		# Update the [[Latest release notes]] page
	# Add the new version to the [[Moodle version history]] page		# Add the new version to the [[Moodle version history]] page
	# Include the new versions in [[Moodle 1.8 release notes]] ~~and~~ [[Moodle 1.9 release notes]]		# Include the new versions in [[Moodle 1.8 release notes]], [[Moodle 1.9 release notes]] and [[Moodle 2.0 release notes]]
	# Notify all registered sys admins		# Notify all registered sys admins
	# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).

Skodak: /* For a stable release on an existing branch XX with point value Y */

2010-12-25T22:56:43Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 22:56, 25 December 2010
Line 13:		Line 13:
	# Edit version.php, update name and version to new point release and commit in the integration repository		# Edit version.php, update name and version to new point release and commit in the integration repository
	# push change to main git repo, github and Gitorious		# push change to main git repo, github and Gitorious
	# sync CVS mirror		# sync CVS mirror (copy the version.php file and update githash.php to point to the release commit)
	# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release		# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release
	# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release		# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release

Skodak: /* For a stable release on an existing branch XX with point value Y */

2010-12-25T22:39:45Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 22:39, 25 December 2010
Line 33:		Line 33:
	# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).
	# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).
	# tag the release in git repositories (integration, main and mirrors)		# final step - tag the release in git repositories (integration, main and mirrors) - to be done by Martin Dougiamas

	One week later:		One week later:

Skodak: /* For a stable release on an existing branch XX with point value Y */

2010-12-25T22:31:55Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 22:31, 25 December 2010
Line 33:		Line 33:
	# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-20840 (for Moodle 1.9.7).
	# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).		# Create a new ('''blocker serious security issue!''') task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).
			# tag the release in git repositories (integration, main and mirrors)

	One week later:		One week later:

Skodak: /* For a stable release on an existing branch XX with point value Y */

2010-12-25T22:27:53Z

For a stable release on an existing branch XX with point value Y

← Older revision		Revision as of 22:27, 25 December 2010
Line 10:		Line 10:

	Release day:		Release day:
	~~# '''cvs -q update -dP'''~~
	# Make sure all the Unit tests pass!		# Make sure all the Unit tests pass!
	# Edit version.php, update name and version to new point release and commit		# Edit version.php, update name and version to new point release and commit in the integration repository
	# ~~'''cvs tag -F MOODLE_XX_MERGED version.php'''~~		# push change to main git repo, github and Gitorious
			# sync CVS mirror
	# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release		# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release
	# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release		# '''cvs tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release
Line 26:		Line 26:
	# Edit download windows/index.php page with new release info (always keeping the "+")		# Edit download windows/index.php page with new release info (always keeping the "+")
	# Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release. This 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].		# Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release. This 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].
	~~# Update the version.php in CVS to be X.X.Y+~~
	~~# '''cvs tag -F MOODLE_XX_MERGED version.php'''~~
	# Add the release date to the [[:Category:Release notes\|release notes]]		# Add the release date to the [[:Category:Release notes\|release notes]]
	# Update the [[Latest release notes]] page		# Update the [[Latest release notes]] page
Line 37:		Line 35:

	One week later:		One week later:
			# Update the version.php in git to be X.X.Y+ during the next weekly PULL process
	# Add all security advisories to [http://moodle.org/security Security news]		# Add all security advisories to [http://moodle.org/security Security news]
	# Add all security issues to the [[:Category:Release notes\|release notes]] with links to security advisories		# Add all security issues to the [[:Category:Release notes\|release notes]] with links to security advisories

Tsala: Development:Major release process link

2010-04-07T11:37:57Z

Development:Major release process link

← Older revision		Revision as of 11:37, 7 April 2010
Line 43:		Line 43:
	# 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]
	# Create a new release notes page for the next version XX.Y+1 (here you can find [[Development:Release notes template\|one template for that]])		# Create a new release notes page for the next version XX.Y+1 (here you can find [[Development:Release notes template\|one template for that]])

	~~===For a major release XX===~~

	~~''To be documented...''~~

	==See also==		==See also==

	* [[Development:Stable branch support]]		* [[Development:Stable branch support]]
			* [[Development:Major release process]]
	* MDLSITE-699: How to repackage one weekly at any moment (a.k.a. "emergency weekly").		* MDLSITE-699: How to repackage one weekly at any moment (a.k.a. "emergency weekly").

	[[Category:Processes\|Release process]]		[[Category:Processes\|Release process]]
	[[Category:Release notes\|Release process]]		[[Category:Release notes\|Release process]]