Versioning and branch management
We need to ensure that we handle versioning and branches consistently. This is what I suggest:
Never code on master; always create a branch for whatever you're working on (in the main repo if you have access, otherwise in your fork), then MR it back into master. After the MR is merged, the merging maintainer should then immediately make a commit to master to bump the version number appropriately. This, and initial commits, should be the only kinds of commit made directly to master.
Edited by Alex Martin