You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We create a v3 branch, that will be for bug fixes and new features. We bump the version based upon https://semver.org policy.
If we make a breaking change or start working on the next major version, then we can start using the develop branch again. This time with the v4.0.0-alpha... versioning.
In summary: (my recommendation)
Use the v3 branch while we work improving the v3.x.y series... once we decide to move onto the next major version: we move back to using the develop branch.
We create a v3 branch, that will be for bug fixes and new features. We bump the version based upon https://semver.org policy.
If we make a breaking change or start working on the next major version, then we can start using the develop branch again. This time with the v4.0.0-alpha... versioning.
In summary: (my recommendation)
Use the v3 branch while we work improving the v3.x.y series... once we decide to move onto the next major version: we move back to using the develop branch.
Hi @da2ce7, OK, then I will follow the release process only until step 7, and create a new v3 branch.
Hi @da2ce7, following the release process what should be the next develop version after v3.0.0-rc.1?
v3.0.1
,v3.1.0
?The text was updated successfully, but these errors were encountered: