> From: Peter Memishian <[EMAIL PROTECTED]>
>
> > I get your point, though -- there are probably reasonable cases that can be
> > constructed where lumping multiple bugs together in a single changeset is
> > going to be immeasurably easier than trying to tease them apart. I think
> > 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.
-JZ
_______________________________________________
tools-discuss mailing list
[email protected]
