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
(update to Moodle version 2.8)
(update, see also)
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_28_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 MOODLE_2X_STABLE branch.


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 in your clone that will track the remote stable branch and switch to it.


     git branch --track local_28_STABLE origin/MOODLE_28_STABLE     (1)
     git branch --track local_2X_STABLE origin/MOODLE_2X_STABLE     (1)
     git checkout local_28_STABLE                                   (2)
     git checkout local_2X_STABLE                                   (2)
     git pull                                                        (3)
     git pull                                                        (3)


Note that you can choose any name for the local branch. In the example above, the local branch is called local_28_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_28_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).
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).


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

Revision as of 06:20, 7 May 2015

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 are using Git, then you must create new local branch in your clone that will track the remote stable branch and switch to it.

   git branch --track local_2X_STABLE origin/MOODLE_2X_STABLE      (1)
   git checkout local_2X_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_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).

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

See also