Trust me, people still call it trunk based development. Just like “agile” has many forms, trunk based development does too.
Managers will often read about some process, tech, or strategy and tout it as the solution to their problems without understanding context nor wanting to invest in what’s actually required for a successful implementation. For example trunk based development should have automated testing, a deployment and a fallback strategy. And if you’re working on something with hefty features that you can’t slice, feature flags or something similar are probably required. Not giving the team time to develop a strategy to implement that is a great way to mess up a product.
What is even the motivation for this? How do you make PRs?
That’s the neat part: you don’t
A joke presumably? Kind of hard to tell!
It’s called “trunk based development”. Look it up and watch videos about it. I swear they are stuck in the 90s yearning for CVS and SVN.
Anti Commercial-AI license
trunk based development generally still merges branches into a main one, see this. idk if only using main even has a name
Trust me, people still call it trunk based development. Just like “agile” has many forms, trunk based development does too.
Managers will often read about some process, tech, or strategy and tout it as the solution to their problems without understanding context nor wanting to invest in what’s actually required for a successful implementation. For example trunk based development should have automated testing, a deployment and a fallback strategy. And if you’re working on something with hefty features that you can’t slice, feature flags or something similar are probably required. Not giving the team time to develop a strategy to implement that is a great way to mess up a product.
Anti Commercial-AI license