docs: outline the release cycle in depth #5214
Conversation
brianp
force-pushed
the
release-cycle
branch
from
07a3b00 to
9d5cd92
Compare
brianp
changed the title
|
This needs more disambiguation for what version numbers mean. MAJOR being for hardforks There's a notable difference here from a pattern we use now where we do not need to manage specific branches for master, stagenet, nextnet etc. Tags in the correct places should be sufficient, long lived branches for these channels don't serve much purpose in this process. If we want to follow gitflow closer then we can reintroduce the maintenance of these branches by making every release branch merge into their channel specific branch. It's still worth noting that things only ever go into those branches, and hotfixes from them. No other work would be done on them. But also that's only if we actually wanted to maintain them. |
brianp
force-pushed
the
release-cycle
branch
2 times, most recently
from
be690fe to
5dd5c32
Compare
Add an extra doc drafting the versioning semantics and how to release a tag for any specific network.
Co-authored-by: Cayle Sharrock <[email protected]>
Make sure the version pattern is explained so people know how to bump a version when needed.
Hopefully it helps.
Co-authored-by: SW van Heerden <[email protected]>
|
@stringhandler ready to go |
Description
Outline in more detail how version tags are managed and the process of releasing a new tag for a particular channel and network.
Motivation and Context
Make sure everyones on the same page regarding tagging best practices, branching, and releasing.
How Has This Been Tested?
It will likely be read, and discussed.