Note: You are currently viewing documentation for Moodle 3.9. Up-to-date documentation for the latest stable version of Moodle may be available here: Upgrade warnings.

Upgrade warnings: Difference between revisions

From MoodleDocs
(removing obsolete template, updating info - needs checking)
(replacing version number with template for automatic updating in future versions)
 
(7 intermediate revisions by 3 users not shown)
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.
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_26_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_32_STABLE, MOODLE_33_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_26_STABLE origin/MOODLE_26_STABLE      (1)
     git checkout -b MOODLE_{{Version2}}_STABLE origin/MOODLE_{{Version2}}_STABLE
    git checkout local_26_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_26_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_26_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 {{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.


For more about how Moodle versions are managed in git and CVS, see our [[dev:Moodle_versions]] page.
For more about how Moodle versions are managed in Git, see our [[dev:Moodle_versions]] page.
 
==See also==
 
* [[Git for Administrators]]


[[es:Advertencias al actualizar]]
[[es:Advertencias al actualizar]]
[[fr:Notifications de mise à jour]]

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_39_STABLE origin/MOODLE_39_STABLE
   git pull

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