This operation can take a while as it is actually getting the entire history of all Moodle versions It creates a new directory named moodle, where it downloads all the files. The upstream repository is called 'origin' by default. the remote server based) moodle.git repository.
Graphical clients are little more than wrappers around the command line version, so you should be able to deduce the correct parameters quite easily. The command line version of Git is discussed here. Generally, the easiest way is to examine the current contents of version.php - substitute the branch in this url, ĭo not use alpha, beta, release-candidates or code from the master branch for production sites. It's important to check that the current state of the branch meets your needs. Soon after the branch is made it will contain 'beta' and 'release candidate' versions of the new Moodle version.
Important: Even though the branch name has 'STABLE' in it, it does not mean that the code on that branch is actually stable. Each release is designated by adding a Git 'tag', for example v3.9.0-beta, v3.9.0-rc1, v3.9.0. The entire lifetime of that version will stay on that branch. Development is generally done on branch 'master'. Major Moodle versions each have their own branch in Git. Once you have downloaded and installed your OS relevant git installation, the git commands in this document should work with your operating system. Support for Git was, up until recently, mostly confined to Linux but builds are now available for most popular operating systems: Getting hold of Git (Windows, OSX, Linux and others) 9.1 Installing a new extension into an existing Moodle.9 Installing and maintaining contributed extensions using Git submodules.8 Installing a contributed extension from its Git repository.6 Updating your installation with minor releases.1 Getting hold of Git (Windows, OSX, Linux and others).
0 kommentar(er)
