Documenting the Git Branch Convention on Smart Contract Repos

🛠 Product Discussions & Suggestions Technical
#1

Because smart contracts tend to have a slower release cycle with larger changes (relative to a front end or cli repo), the Aragon contract repos use a unique Git Branch convention.

For all Smart Contract Repos:

(Including dao-kits, aragon-apps, excluding AragonOS)

  • next: This branch collects changes which are ready for security review, and to be merged to master
  • master: Code in this branch has been deployed to the Ethereum main net, and can be assumed to have undergone security review.

For the AragonOS Repo:

  • dev: This branch is effectively the same as next in other repos. But it is the default branch in github so that app developers can easily find and build on upcoming changes.
  • master: Same as above.
3 Likes
Git branch convention for Aragon repos
#2

aragonOS has now also moved to the next branch notation, but keeps its default branch as next for development purposes (master serves as the audited and production-ready branch for older releases; all releases are made from master).

3 Likes