28 | | Boost strongly encourages that the main development branch be named "develop". |
| 28 | Releases for both the super-project and individual libraries are always on branch {{{master}}}. {{{master}}} in the library's {{{boostorg}}} public repo should be stable at all times, so should only be pushed to the library's public repository when it is stable and ready to ship. |
| 29 | |
| 30 | Branch {{{develop}}} is the main development branch. Whether or not {{{develop}}} is stable in the library's public {{{boostorg}}} repository is up to the library maintainer. |
| 31 | |
| 32 | Additional branches, if any, are up to the library maintainer. See the discussion of Git Flow, below. |