4 ms·
The TBD [0] crowd disagrees with you. I agree with you though. Not that I don't see the value proposed by TBD, but I think you can have >90% of said value and
by cassianoleal 4y ago
The TBD [0] crowd disagrees with you.
I agree with you though.
Not that I don't see the value proposed by TBD, but I think you can have >90% of said value and none of the downsides using a well thought out branching strategy.
[0] Trunk-Based Development: https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
- smallnix 4y agoFrom the linked Website: > Depending on the team size, and the rate of commits, short-lived feature branches are used for code-review and build checking (CI). [...] Very small teams may commit direct to the trunk.
- cassianoleal 4y agoIndeed. That seems to be a new-ish addition. I'm glad they now admit alternate approaches.
- liuliu 4y agoTBD doesn't mean you have a red CI main branch. Of course it is always green on main. It means you have short lived feature branch and rely on runtime checks for feature gating. A broken main will halt TBD. You are mischaracterize what TBD is.
- cntainer 4y agoI'm in the "continuously improve the team's process to best suit its needs" crowd. Sometimes TBD is the answer, sometimes you need something else. What I did notice is that, with time, mature teams end up simplifying processes in order to reduce friction and increase output.