Trunk only goes well with continuous deployment. If each increment in deployment is small enough, then you know exactly when things break and rollbacks are eas

Trunk only goes well with continuous deployment. If each increment in deployment is small enough, then you know exactly when things break and rollbacks are easy. The 3-2-1 system where you develop for 3 months, then merge for 2 months, then debug in production for 1 month, is a real drag, and doesn't lend itself to quick feedback at all. For a software looking for product market fit with ultra short cycles, I would absolutely choose trunk only. For engineering projects in areas where cycles are months, or years, more traditional branching makes more sense.