2min chapter

Software Engineering Radio - the podcast for professional software developers cover image

SE Radio 564: Paul Hammant on Trunk-Based Development

Software Engineering Radio - the podcast for professional software developers

CHAPTER

The Implications for Bank-Based Development

Tribal development teams never freeze the trunk ever. The a-commit or commits get cherry-picked to it which is a specialized form of merge that Git has, mercurial has but not release branches. A policy change means devs shall not develop on the release branch. So we said already we don't want additional features rammed in after the branch cut moment. But we are open to bug fixes going in because somebody in the proving cycle for the release that's about to go out this couple with that release branch has found a defect. We have fixed that in the trunk. That was unplanned work. It may be able to test as well because we're really good test driven

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode