Closed dougbu closed 7 years ago
We should do what we do everywhere in ASP.NET Core: dev
is the newest branch, and we'll create branches for stabilization, and tags for releases.
@Eilon I've merged master
into dev
. Please set dev
to be the repo's default branch. Then, I'll delete master
and this issue can be 3 - Done
.
Ok dev
is now the default branch. Please take this into account regarding any open PRs (because they'd all be on the wrong branch now).
master
is no more and all PRs are focused on dev
.
@Eilon the
dev
branch in this repo was previously ahead ofmaster
by six commits. Both were ahead of the1.2.1-rtm
tag though just by one commit inmaster
's case. In any case, the history was very linear and that's no longer the case because PR #158 (922798f6) merged intomaster
but notdev
.Should I merge / cherry-pick this commit / whatever to again place
dev
ahead ofmaster
?Or, would you prefer I bring the newer commits over from
dev
tomaster
, then kill thedev
branch (with fire)? I suggest we don't need to have bothdev
andmaster
, given the well-kept tags for older releases.