Software Code Branch

Context:
- It can range from being a Short-Lived Code Branch to being a Long-Lived Code Branch.
- It can follow a Code Branching Strategy.
- ...
Example(s):
- a Development Branch.
- a master Branch.
- ...
See: Continuous Delivery, Branching (Software), Software Release Train, Lean Software Development, Software Release, Feature Toggle.

References

(Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/Continuous_delivery#Principles Retrieved:2022-10-26.
- ... Other useful techniques for developing code in isolation such as code branching are not obsolete in a CD world, but must be adapted to fit the principles of CD - for example, running multiple long-lived code branches can prove impractical, as a releasable artifact must be built early in the CD process from a single code branch if it is to pass through all phases of the pipeline.

(Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/Rolling_release#Rolling_release Retrieved:2022-10-26.
- ... A rolling release is typically implemented using small and frequent updates. However, simply having updates does not automatically mean that a piece of software is using a rolling release cycle; for this, the philosophy of developers must be to work with one code branch, versus discrete versions. When the rolling release is employed as the development model, software updates are typically delivered to users by a package manager on the user's personal computer, accessing through the internet a remote software repository (often via a download mirror) stored on an internet file server.