Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U6YPB4SJX>: a 3rd option that is worth discussing (even though we moved away from it in the past) is: twitter could begin consuming nightlies rather than releases. this is a variant of your item 2, but because twitter would not be consuming releases, releases would be no more trustworthy than any other commit in master.

for posterity, this was the motivation for that: <https://groups.google.com/d/topic/pants-devel/axaMpP-Z8nU/discussion>

afaik, this variant would not require any particular branching strategy, because you could mostly just "push the button" on any nightly that was green, rather than necessarily needing to be green on a friday during a `dev` release