| |||||||||||||
A tale of two release cyclesA tale of two release cyclesPosted May 4, 2007 18:28 UTC (Fri) by JohnNilsson (guest, #41242)Parent article: A tale of two release cycles
Some time ago I suggested a merge queue model. Here's a variant on that theme.
If a regression is found. Always remove the code that introduced it and refuse to merge it before the regression is gone. The basic principle being that this would create an incitement to fix the regression if people want the code merged.
(Log in to post comments)
|
|||||||||||||