Олег Давидович: 1 версия импортирована

2024-10-21T08:51:26Z

1 версия импортирована

← Предыдущая версия	Версия от 08:51, 21 октября 2024
(нет различий)

1>Tsala: content copied from Development:Release_process

2010-04-07T11:10:25Z

content copied from Development:Release_process

Новая страница

{{Template:Work_in_progress}}

This page describes the standard procedures for making a major release e.g. Moodle 2.0.

==Beta release==

''To be documented...''

# [[Development:Weekly Code Review|Test / QA]] etc

==Final release==

''Additional points to be added...''

One week before:
# Notify Moodle developers and Moodle Partners about the upcoming release
# 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 [[:Category:Release notes|release notes]] of the upcoming version.

Release day:
# '''cvs -q update -dP'''
# Make sure all the Unit tests pass!
# Edit version.php, update name and version to new point release and commit
# '''cvs tag -F MOODLE_XX_MERGED version.php'''
# '''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 -q update -dP''' all code on download server
# Run moodle-makenightlystableXX
# Go to download/stableXX
# Copy current daily as release package:
## '''cp moodle-latest-XX.zip moodle-X.X.Y.zip'''
## '''cp moodle-latest-XX.tgz moodle-X.X.Y.tgz'''
# Edit download index.php page with new release info and links
# Run moodle-makewindowspackages so all the windows packages will be rebuilt
# 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].
# 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]]
# Update the [[Latest release notes]] page
# Add the new version to the [[Moodle version history]] page
# 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
# 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).

One week later:

# 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
# 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]
# 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]])

==See also==

* [[Development:Release process]]

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

Development:Major release process - История изменений

Олег Давидович: 1 версия импортирована

1>Tsala: content copied from Development:Release_process