I've worked in both "feature branch" and "trunk only" development shops, and I haven't had as good of an experience with trunk only. On one project, I made architectural changes that worked well for the main repo... but there were countless one-off scripts that I had no knowledge of (because they weren't committed, or rebasing didn't happen often) that broke. It was a ~happy~ horrible experience. The second "trunk only" project I worked was in another group where communication was poor with remote employees, myself included. Big changes would happen without notice, I would get asked to undo hours or days of work because it broke code someone else hadn't checked in "because they don't do that until code is finished."
All that being said, I agree with your original premise - it works well when the team communicates well. Both of my experiences were the result of poor communication.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've worked in both "feature branch" and "trunk only" development shops, and I haven't had as good of an experience with trunk only. On one project, I made architectural changes that worked well for the main repo... but there were countless one-off scripts that I had no knowledge of (because they weren't committed, or rebasing didn't happen often) that broke. It was a ~happy~ horrible experience. The second "trunk only" project I worked was in another group where communication was poor with remote employees, myself included. Big changes would happen without notice, I would get asked to undo hours or days of work because it broke code someone else hadn't checked in "because they don't do that until code is finished."
All that being said, I agree with your original premise - it works well when the team communicates well. Both of my experiences were the result of poor communication.