We should replace this with an arbitrary integer stored in a config variable, which gets incremented whenever we upgrade the site. This would have the added (minor) benefit that you could then force a reloading of all the assets without incrementing the major version number, by simplying increasing this integer.

Only low importance, because a hacker could probably infer the Mahara version number anyway, by looking at changes in the site's behavior.

We need to make a change to that patch that was backported, to make sure that it's safe to run it multiple times. Currently it resets the cacheversion every time, which could mean that the cacheversion gets rewound to an earlier state and overlaps with an older cacheversion.

Here are all the patches that add cacheversion. We'll need to add a bit more logic to the ones for 1.9_STABLE, 1.10_STABLE, and master. (1.8_STABLE is okay because it can't overrun an earlier version.)