News for hackers. Stuff that matters.
Re:Trunk-Based Development by paul_h on Sunday January 29, 2017 @03:16PM (#13516326)
> Those have release branches.

Some Trunk Based Development teams do "branch for release" https://trunkbaseddevelopment.com/branch-for-release/ and some do "release from trunk" https://trunkbaseddevelopment.com/release-from-trunk/

Google gave numbers themselves - 95% of their devs are in one big trunk (formerly perforce, but re-written in-house in 2012). It's true that the open source facing teams are outside that, and have processes that are less lock-step than what they do in-house.

Android - Samsung, on each release (maybe not anymore), used to check all the composite parts of Android into one big trunk for themselves. Back into their Perforce.

> If you're making Google Chrome, you don't.

There's nothing stopping the Chrome team from doing Trunk Based Development on Github, and accepting unsolicited pull requests like any other team.

Re:Trunk-Based Development by paulddraper on Sunday January 29, 2017 @03:20PM (#13516347)
You can have long lived release branches in "trunk-based development"?!?

In that case, I guess I haven't ever seen a branching strategy that wasn't "trunk-based." What would that even be?

Re:Trunk-Based Development by qwer on Sunday January 29, 2017 @03:46PM (#13516530)
Anything involving long-lived feature branches especially ones with multiple collaborators, eg git-flow.
Re:Trunk-Based Development by paulddraper on Sunday January 29, 2017 @05:11PM (#13517057)
If I understand git-flow correctly, it's a trunk (develop) with a release branch (master).
Re:Trunk-Based Development by paul_h on Sunday January 29, 2017 @06:53PM (#13517598)
Re:Trunk-Based Development by paulddraper on Sunday January 29, 2017 @07:21PM (#13517703)
Guess I should have RTFM.

Well written.

Re:Trunk-Based Development by paul_h on Sunday January 29, 2017 @03:56PM (#13516597)
It depends on whether the branch ever merges back to the trunk or not.