Open vncoelho opened 1 month ago
You need create a new branch for releases when it time. Not only setting the tag
in master
. But creating this branch.
configurations
.bug fixes
.github
workflow actions
.master
. (if any hotfixes)nuget
. (like v3.7.0, v3.7.1, v3.7.2, v3.7.3, v3.7.4 to just get deleted)release/v3.8.0
release/v3.9.0
release/v3.10.0
release/v3.11.0
Exactly, @cschuchardt88
Perhaps some commits since 3.7.4 could had been merged in a kind of development branch, while any necessary minor fix would directly go to master.
Normally you have a development
branch. Where each member
has it own
branch; branching off the development
branch.
Now that all basic components are here in the neo-core, we depend in this repo in different ways.
Without proper UTs, Integration Tests and verification on neo-cli, we will often need hotfix on minor things after a MAJOR release. In particular, things become too much complex when we need to add new feature or refactors and we still need minor fix on main branch.
In mind of minor fixes, or even major ones, I would like to highlight, at least, the following:
Perhaps some commits since 3.7.4 could had been merged in a kind of development branch, while any necessary minor fix would directly go to master.
We could let a PR open with a per-defined title -> DEVELOPMENT BRANCH: NEXT MAJOR 3.X.X