Not 'Obtaining the code from Git" in entirety.
moodle directory already has hidden .git directory and code was acquired for the 3.4.highest version at the time of installation.
To upgrade to 3.5.0 when released and you have determined that plugins/addons installed are compatible with 3.5.0 , one has to:
git branch --track MOODLE_35_STABLE origin/MOODLE_35_STABLE
git checkout MOODLE_35_STABLE
Check the branch: git branch -a to see if the * is on branch desired.
In this example, git pull would acquire the 3.5.0 code.
To check: fgrep '$release' version.php
Then use the script in moodlecode/admin/cli/ to actually upgrade.
If one keeps their site up to date, suggest creating 2 bash shell scripts to: 'update' and one more for 'upgrade'
As would be a good practice, the first lines of those scripts would make a backup of code and a backup of the DB (sql dump).
It would be a good idea to run cron just prior to the backups. It would also be a good idea to put the site in the maintenance mode right in the 'update' or 'upgrade' scripts. Both one can do with scripts in moodlecode/admin/cli/
Feel free to use:
as a starting place if you like.
'spirit of sharing', Ken