Discussion: drop of develop branch
Closed this issue · 6 comments
Currently, I am very confuse on the master vs develop branch. It looks no specific development workflow.
If no objection, I will delete the develop branch and all change target for the next release should send PR to master.
For feature development, let keep current convention of prefix with feat
which is clear.
For patch we need to release to existing chain, we should patch the current master too. So of the nature of the blockchain, we will only keep one production branch, which is codename, like current sheungwan
, fotan
.
@williamchong @nnkken thought?
Current default is master branch now. Will delete the develop branch.
yes, for the codename
branch should we use sementic prefix like v1.x.x-fotan
for easier searching?
I think we can start with v1.2.0-fotan. Just keep the old branch as it.
And in next non-binary compatible release, i.e. the Prefix change and cosmos sdk v0.44 upgrade. v2.x.x-{codename}
I think major version tracking branch should be v1-fotan, v2-laichikok, v3-shatin, v4-taipo, etc?
Yes that make sense