The separate 'dev' branch can cause problems/annoyance for little benefit:
PRs default to 'master' and people have to explicitly change it to dev each time.
Releases are a more complicated process of rc branch->dev, then dev->master.
From now on, we'll PR directly to master which is now the 'unstable' branch. Things should generally work in master (and hopefully we'll get CI setup someday). Stable releases are always tagged and listed in github releases. This matches most github projects that I'm familiar with.
The separate 'dev' branch can cause problems/annoyance for little benefit:
From now on, we'll PR directly to master which is now the 'unstable' branch. Things should generally work in master (and hopefully we'll get CI setup someday). Stable releases are always tagged and listed in github releases. This matches most github projects that I'm familiar with.