@neuecc With the removal of NB.GV, it's no longer clear to me which version master builds vs. develop. Can you teach me where I can refer in a branch to see what version would be built?
The PR checks build 1.0.0 versions, it seems.

I like to know whether a branch will target 3.0, 3.1, or something else. Sometimes folks want to know what version (or at least what version band) will include the fix. And I find it useful sometimes when deciding whether a PR should target master or develop.

Oh, it seems the branch management has been operating based on intuition/feeling, and nobody except you seems to understand those rules.
And currently, there are no rules in place at all.

@neuecc So is the idea at present the same as it was before, where master is where to make fixes that should release soon, and develop is where to work on features?

For large-scale updates/refactoring, we might use the develop branch, but since we'll probably just have small fixes for a while, I think working with master branch only should be fine.

Oh, another reason to know the version for a given branch is so I can pick the right milestone on the PR to record the version that will include it. At the moment, the milestones available are 3.0 and 3.1.