>>> that with some discipline, those cases will appear infrequently, though as >>> a gate policy, I think that we should work gently towards one changeset <-> >>> one bug slowly >> >> Please no. This would be a disastrous drain on productivity. > > I concur. > > Currently, an engineer working on a change will often address one or > more other minor CRs in the same files. The incremental cost of these > additional fixes is reduced to extra edits, the additional tests, and > the bookkeeping for the bugs, with no extra builds, no extra downloads, > no overhead in resolving problems found in tests or bringover/pull > conflicts. The one changeset == one bug discipline eliminates such > economies of effort.
Exactly -- and sometimes testing comes for free as well. If anything, we should be going in the other direction, finding ways to *encourage* developers to throw in some additional bugfixes while they're "in the neighborhood" -- and making the cost of doing so as minimal as possible. -- meem _______________________________________________ tools-discuss mailing list [email protected]
