Development Ethos

[CommonClimate]

It appears that our development style has been slightly unorthodox. The good folks at QuanSight, particularly Kim Pevey, have made the following suggestions:

1. removing the development branch
2. each new feature gets a branch
3. branches are small and short-lived
4. master should be a protected branch
5. any commits must go through a PR
6. PRs must be reviewed by at least one person and get approval
7. CI must be passing before merging a PR

Most of those are things we (Jan 26 USC lab meeting) agreed on, though @khider objected to protecting the master branch, so I'll let her elaborate here. In any event, it will take everyone, particularly me, quite a bit of effort to forge these new habits, but resolutions are in theme for January.