✳flâneur — a map of the web's best reading

Five-minute overview - Trunk Based Development

trunkbaseddevelopment.com · 967 words · saved by 1 readers

Assuming any network-accessible source control, physical distance is mitigated by AV technologies including screen sharing. So we will not worry about that so much these days. Frank’s ‘distance’ is about the distance to the integration of code from multiple components/modules/sub-teams for a binary that could be deployed or shipped. The problematic distance is to code not yet in the single shared branch, that might: Trunk-Based Development is a branching model that reduces this distance to the minimum. Notes There are many deciding factors before a development team settles on Trunk-Based Development, but here is a short overview of the practices if they do: Trunk-Based Development will always be release ready If an executive manager visited the development team and commanded “Competitor X has launched feature Y, go live now with what we have”, the worst response would be “give us one hour”. The development team might have been very busy with tricky or even time-consuming tasks (therefo

Five-minute overview Distance Branches create distance between developers and we do not want that — Frank Compagner, Guerrilla Games Assuming any network-accessible source control, physical distance is mitigated by AV technologies including screen sharing. So we will not worry about that so much these days. Frank's 'distance' is about the distance to the integration of code from multiple components/modules/sub-teams for a binary that could be deployed or shipped. The problematic distance is to code not yet in the single shared branch, that might: break something unexpected once merged be diffi

Explore this link on the map →

related reading