Difference between revisions of "Upgrade warnings"

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 3.3. Up-to-date documentation for the latest stable version of Moodle is probably available here: Upgrade warnings.

m (fr link)
m (Update Moodle version and simplify)
Line 1: Line 1:
 
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 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 MOODLE_2X_STABLE branch.
+
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_30_STABLE, MOODLE_31_STABLE etc).
  
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.
+
If you are using Git, then you must create new local branch that will track the remote stable branch and switch to it.
  
     git branch --track local_2X_STABLE origin/MOODLE_2X_STABLE      (1)
+
     git checkout -b MOODLE_30_STABLE origin/MOODLE_30_STABLE
    git checkout local_2X_STABLE                                    (2)
+
     git pull
     git pull                                                       (3)
 
  
Note that you can choose any name for the local branch. In the example above, the local branch is called local_2X_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_2X_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).
+
Replace 30 with the relevant Moodle version. At the first line, the new local branch MOODLE_30_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.
 
For more about how Moodle versions are managed in Git, see our [[dev:Moodle_versions]] page.

Revision as of 19:31, 14 March 2016

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_30_STABLE, MOODLE_31_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_30_STABLE origin/MOODLE_30_STABLE
   git pull

Replace 30 with the relevant Moodle version. At the first line, the new local branch MOODLE_30_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.

See also