mithril.js icon indicating copy to clipboard operation
mithril.js copied to clipboard

Published 20 hours ago • verified publisher icon MithrilJS

Branch naming scheme

Open pygy opened this issue 3 years ago • 1 comments

As previously discussed in Zulip (and as described by @JAForbes here), we should create next and release branches for v1 and v2 releases once v3 is out.

I suggest we go for v1-next => v1-release, and v2-next => v2-release.

We could also rename master and go for a next => release pair. AFAICT since the only PR we have against master is pr-release's renaming it should not be too hard. I'll do experiments in a side repo and see how GH and pr-release deal with branch renames. If it proves problematic, we can do it just after v3 is released.

Does this sound fine?

pygy avatar Jun 13 '22 16:06 pygy

Sounds good, I think it will be straightforward but always good to test in another repo.

JAForbes avatar Jun 14 '22 01:06 JAForbes