I'm proposing to start using develop branch for development and update the master branch only before the release.
That will help in scenarios where some minor fixes should be release ASAP without publishing anything else. One could create a branch from the previous release tag, but having two separate branches will align the project with other kotlinx-projects.
To make sure that everyone is on the same page, I'm adding a guideline.
I'm proposing to start using
developbranch for development and update themasterbranch only before the release.That will help in scenarios where some minor fixes should be release ASAP without publishing anything else. One could create a branch from the previous release tag, but having two separate branches will align the project with other kotlinx-projects.
To make sure that everyone is on the same page, I'm adding a guideline.