Consider moving to a stable branch strategy instead of just master branch

[brendanheywood]

hi @paulholden

Would consider swapping to this branch strategy? The main reason for this is so we can point each site on a given version and git pull updates for that branch on a regular basis, but we don't want to break an old site if the master branch drops support for that old moodle version.

If you don't want to have the effort of branching at every major moodle version, we use a hybrid: we don't branch at every version we only branch when core api's change and we are forced to. eg we might have MOODLE_STABLE_401 which supports 4.1 - 4.4 and then we'd cut a branch MOODLE_STABLE_500 if it was needed.

Some examples of this:

https://github.com/catalyst/moodle-mod_reengagement?tab=readme-ov-file#branches

https://github.com/catalyst/moodle-tool_objectfs?tab=readme-ov-file#branches