Associating bugs with changesets

[Greg Ward]

On Tue, Jun 2, 2009 at 11:39 AM, Arne Babenhauserheide <arne_bab at web.de> wrote:
> On Tuesday, 2. June 2009 14:36:42 Greg Ward wrote:
>> * we're planning a multi-repository workflow, with all changes
>> eventually landing in a master repository.  Corrections would take
>> some time to propagate to all repositories, so different people will
>> have different changeset/bug mappings at different times.
>
> Would that be a problem?

Don't know, since this is all hypothetical right now.

> Who does QA corrections?

Theoretically developers will do them when they realize they goofed;
in reality, it'll probably be me or one of the other two people who
actually understands the whole workflow and toolchain.  (At least,
that is how things currently work with CVS.  I know that Hg is
markedly more sensible than CVS, but I still expect most developers to
have only a vague sense of how their day-to-day work wends its way
through our build system and QA to customers.)

> How does the correcting interleave with the general workflow?

Again, not yet known.

Thanks for your ideas!

Greg