This task corresponds to point #3 of:

http://docs.moodle.org/dev/Major_release_process#One_week_before

And it's achieved in a semi-automated way with the "versions_check_set.sh" script available @ https://github.com/moodlehq/moodle-local_ci/blob/master/versions_check_set/versions_check_set.sh

1) In a git, working, master site with the ci local plugin installed.

2) Define and export all the env variables required by the script.

• $WORKSPACE: Path to the directory where test reults will be sent (/tmp)
• $phpcmd: Path to the PHP CLI executable (/usr/bin/php)
• $gitdir: Directory containing git repo (the dirroot of the git, working site)
• $setversion: 10digits (YYYYMMDD00) to set all versions to. Empty = not set

3) Run it. With errors, they will be reported and fixing will be necessary. (look for ERROR in the $WORKSPACE/versions_check_set.txt file and/or check exit status of the script)

4) Without errors, all the versions, requires and dependencies will be bumped.

5) Commit

6) Note that the main version file is NOT updated at all. One extra commit bumping it may be necessary.

7) Run the checker again to verify that there are no errors and no more changes are performed.

Note the checker is also run periodically by the ci server and also as part of the "remote_branch_checker", so normally all the version.php files should be under control.

(This issue will be cloned for each major release).

Ciao