Description
Post v5 stable release, we will resume releasing from two branches.
Here are some notes based on the Discord conversation about this.
In the master branch, we would accept only bug fixes for the current stable major/minor release.
In practice, the first one would be v5.0.1.
The next minor would be a separate release branch (example v5.1) with an open pull request to master.
Alpha/beta can be released from that branch and the branch should always be rebased on top of the master.
Fixes to the master branch should automatically be released. One revision should contain only one fix and once merged to master, an automated NuGet push and GitHub release should be created.
Contributors of a fix would need to update the ChangeLog with a new revision version, but I don't think that is going to be a huge hurdle.
Alpha/Beta releases could potentially also be automated, although I wouldn't release those every time when a PR is merged. More on a "makes sense to try out" basis.
@baronfel @TheAngryByrd any pointers to create automated releases.
//cc @dawedawe