Frequency Git Workflow
Source Diagram: https://docs.google.com/drawings/d/1GyvodIcZ3AfrfmpgK465N369Lu-F41Ni-__Gvk4p6iQ
This page describes Git branching workflow employed by the Frequency team during development and release cycles. This workflow has two types of long-lived branches:
- "Release Branch" – this branch corresponds to the specific Polkadot release version, e.g.
v0.9.29,v0.9.30, etc. - "Next Branch" – this branch represents the next version under development, i.e. a release candidate
| Number | Branch Name | Branchnbsp;Pattern | Purpose |
|---|---|---|---|
| 1 | Release Branch | release-vx.x.x* |
Corresponds to a given released Polkadot version, e.g. release-v0.9.29, release-v0.9.30, release-v0.9.30-1, etc. |
| 2 | Next Branch | origin/main |
Represents release candidate - the next version of the chain under development |
Once a long-lived branch is created, it can stay in the repo forever. In other words, there is no time limitation on the lifecycle of such branch.
Coming soon...
Coming soon...