Version control branches?

[ericasaw]

I know most of these hooks are maintained individually, but it might be nice with each new version branch of MESA to create a new version branch here as well. That way when the procedures are (or are not) updated with each version they are tagged/included appropriately with the versions of MESA they are compatible with. It would help to make it more clear when a specific procedure is no longer being maintained for newer versions of MESA.

[warrickball]

I'm planning to start tagging the relevant commits on the release branch. Updating release should give you something that works with the latest version and something like git checkout r21.12.1 should get the state of release before it was updated for whatever was the next version. This has simply been too low priority for me to work on and I'm currently the only maintainer.

This structure might seem slightly odd but it has to allow people to contribute hooks for the current release, so we can't fix the tag for the current version until the next version is released.