![]() # Check which branch you are currently tracking You should put your site into maintenance mode, or disable the website, before starting the upgrade. This will also download the changes for newer Moodle versions (but not yet make use of them). You should ensure that you have updated your installation with the latest minor release of your currently installed Moodle version first (as described in the section above). When you want to upgrade to a newer major release, you will need to tell your git installation to track the newer release instead of the release that you currently have installed and are tracking. If this is a production site you should still consider the Upgrade instructions (e.g. To update your code to the latest version (on the MOODLE_401_STABLE branch) all you have to do is: Check the shortlog to see if the official repository has been already updated or not. On Wednesday you can install all patches by updating your code. The Moodle development team performs integration and testing of fixed bugs every Monday and Tuesday. Updating your installation with minor releases It's a bit slower, so use the Git protocol if you can. If this is a problem, you can use GitHub's http version. Git uses a read-only protocol that may be blocked by your firewall (port 9418). Note that Git has a huge number of options for each command and it's actually possible to do the above process with a single command (left as an exercise!!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |