News for hackers. Stuff that matters.
Re:How Chromium Works by lmm on Saturday September 26, 2015 @07:22AM (#10282769)
How long does a single dev typically go between applying their changes to master? Minutes, hours, days, weeks? If you have a big change to work on do you put it in master behind a feature flag, do the whole thing and then rebase, or what?

Do developers ever want to collaborate on an in-progress feature before it's ready for master? As far as I can see the only real difference between your workflow and a github-flow-like workflow is that they can't do that because their feature branches are local.

Re:How Chromium Works by aboodman on Saturday September 26, 2015 @10:21AM (#10283163)
Features can take months and involve many people. In that case it will be worked on behind a feature flag on master.

There is no such thing as "not ready for master" in the chromium workflow, only "not ready to be enabled by default".