Upgrade warnings: Difference between revisions

From MoodleDocs
(removing obsolete template, updating info - needs checking)
(replaced version 26_STABLE to 27_STABLE)
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_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 MOODLE_27_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_26_STABLE origin/MOODLE_26_STABLE     (1)
     git branch --track local_27_STABLE origin/MOODLE_27_STABLE     (1)
     git checkout local_26_STABLE                                   (2)
     git checkout local_27_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_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).
Note that you can choose any name for the local branch. In the example above, the local branch is called local_27_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_27_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 and CVS, see our [[dev:Moodle_versions]] page.


[[es:Advertencias al actualizar]]
[[es:Advertencias al actualizar]]

Revision as of 14:01, 3 July 2014

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_27_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_27_STABLE origin/MOODLE_27_STABLE      (1)
   git checkout local_27_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_27_STABLE. At the line (1) the new local branch is created and set to track the remote branch MOODLE_27_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.