Comment 3 for bug 1214124

Seems like a decent approach. The get_config('release') value goes up with each minor release, which is the most likely time that people will deploy new versions of Mahara. And in between minor releases, the version number gets changed to e.g. 1.7.3testing, which again is different, so if admins deploy a minor release and then update to HEAD before the next minor release, they'll get another version number.

I suppose if we want to be really complete on this, we should adopt a policy that if you push a commit that changes static assets, you should increment the release number e.g. 1.7.3testing1 1.7.3testing2, etc.