I'm fine with this.
- We'll define four new labels for GitHub PRs:I suggest that the "mergeable" bot prints a reminder of this in the PR, unless the PR already has one of these labels. The following paragraph may be good to include in that reminder as a help to choose the correct label:
There's some judgement involved in this labelling process. An algorithmic change might change behavior enough to add a new feature (`Feature`) or cause issues for downstream code (`Breaking Change`). On the other hand, changing a class API by marking methods as deprecated for future removal is not a breaking change _yet_, and can be marked as `Fix`.
Set Github protections so master cannot accidentally be updated by PRsCan we developers stay on master and make PRs to master, or should we make PRs against some other branch? I'm asking to make sure I understand the process.