Closed timrourke closed 7 years ago
Yes, thanks for bringing it up @timrourke 👍 That is the plan once we release the first stable version. It was too early to adopt IMO, as we are still in beta phase.
Currently we are using beta branches, which could be seen as the develop
branch and master serves for releases only. Features should currently be pointed to v1.0.0-beta.4
for the next beta release.
I will add this to the Contributing document soon, so we are prepared once we release this.
👍 Sounds great! Makes sense - no reason to deal with the formality overhead until the first release!
I propose that this library adopt the discipline of Git Flow as the means of managing pull requests, branches, and releases. This approach should:
https://datasift.github.io/gitflow/IntroducingGitFlow.html