| ▲ | myelin 3 days ago | |
The Chromium commit queue slightly predates this -- they started using it in 2010. | ||
| ▲ | masklinn 3 days ago | parent | next [-] | |
while the article does not provide specific dates for the “prehistory” the Not Rocket Science piece refers to an automated integration system working circa 2000~2001: > February 2 2014, 22:25 […] Thirteen years ago I worked at Cygnus/RedHat […] Ben, Frank, and possibly a few other folks on the team cooked up a system [with a] simple job: automatically maintain a repository of code that always passes all the tests. | ||
| ▲ | anp 2 days ago | parent | prev [-] | |
(I work on a project that uses Chromium’s commit queue infrastructure) I think there’s a big difference between Chromium’s approach and the “not rocket science” rule. AIUI Chromium’s model there are still postsubmits that must pass or a change will be reverted by a group monitoring the queue. This is a big difference in practice vs having a rotation or team that reorders the merge queue and rolls changes up to merge together. In the commit queue model you land faster at the expense of more likely reverts than in the merge queue model. | ||