Hacker News new | ask | show | jobs
by icco 5589 days ago
This is interesting. What I'm curious about though, is how does this workflow scale to thirty developers? 100?

I tend to believe with six people or less, you can really work together with any system and it will work fine. Some will obviously require more work than others, but once you get to a larger team, some systems just won't work, AFAIK.

1 comments

From my experience with working with 50+ developers, organized into teams of 3-8 people: Feature branches are the way to go. We used an adapted version of the git-flow workflow and it does scale pretty nicely.
I like Gitflow alot, how did you guys adapt it? Was anything major required to get it to scale up to 50+?
We experimented with team branches to integrate work of the subteams before merging into develop, but that did not work out very well
Very cool. What do you guys use for issue management?
We used Agilo, and it sucked