Upgrade warnings: Difference between revisions

Latest revision as of 06:41, 1 September 2017

If you reached this page from a warning during an upgrade from a stable version then it's probable that some of our branch changes have affected you.

If you intend to stay with the most recent stable version of Moodle, then you need to switch your checkout over to use the appropriate MOODLE_3x_STABLE branch (such as MOODLE_32_STABLE, MOODLE_33_STABLE, etc).

If you are using Git, then you must create new local branch that will track the remote stable branch and switch to it.

   git checkout -b MOODLE_37_STABLE origin/MOODLE_37_STABLE
   git pull

Replace 37 with the relevant Moodle version. At the first line, the new local branch MOODLE_37_STABLE is created and set to track the remote branch of the same name. At the second line, the git-pull command fetches recent changes from the upstream and merges them into your local branch. To update your Moodle next week, you can run just this second line.

For more about how Moodle versions are managed in Git, see our dev:Moodle_versions page.

@@ Line 1: / Line 1: @@
+{{Installing Moodle}}
 If you reached this page from a warning during an upgrade from a stable version then it's probable that some of our branch changes have affected you.
-From November 2010 until March 2011 we were using the "master" in git (HEAD in CVS) to work on the stable version of Moodle 2.0.x.  In March 2011 we split the stable development to a separate branch called MOODLE_20_STABLE (see diagram below).
+If you intend to stay with the most recent stable version of Moodle, then you need to switch your checkout over to use the appropriate MOODLE_3x_STABLE branch (such as MOODLE_32_STABLE, MOODLE_33_STABLE, etc).
-If you intend to stay with the most recent stable version of Moodle, then you need to switch your checkout over to use the MOODLE_20_STABLE branch. If you are using CVS, then use
+If you are using Git, then you must create new local branch that will track the remote stable branch and switch to it.
-     cvs -q update -dPr MOODLE_20_STABLE
+     git checkout -b MOODLE_{{Version2}}_STABLE origin/MOODLE_{{Version2}}_STABLE
+    git pull
-If you are using Git, then you must create new local branch in your clone that will track the remote stable branch and switch to it.
+Replace {{Version2}} with the relevant Moodle version. At the first line, the new local branch MOODLE_{{Version2}}_STABLE is created and set to track the remote branch of the same name. At the second line, the git-pull command fetches recent changes from the upstream and merges them into your local branch. To update your Moodle next week, you can run just this second line.
-    git branch --track local_20_STABLE origin/MOODLE_20_STABLE      (1)
+For more about how Moodle versions are managed in Git, see our [[dev:Moodle_versions]] page.
-    git checkout local_20_STABLE                                    (2)
-    git pull                                                        (3)
-Note that you can choose any name for the local branch. In the example above, the local branch is called local_20_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_20_STABLE. At the line (2) we switch to the newly created branch. At the line (3) the git-pull command fetches recent changes from the upstream and merges them into your local branch. To update your Moodle next week, you can run just the line (3).
+==See also==
-For more about how Moodle versions are managed in git and CVS, see our [[dev:Moodle_versions]] page.
+* [[Git for Administrators]]
-[[Category:Site administration]]
+[[es:Advertencias al actualizar]]
+[[fr:Notifications de mise à jour]]

Documentation

Upgrade warnings: Difference between revisions

Latest revision as of 06:41, 1 September 2017

See also