[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tracker 1686 - Process question - separate Tracker Issues or handlep
Re: Tracker 1686 - Process question - separate Tracker Issues or handlepatches as part of T1686?
Sun, 6 Nov 2011 17:41:53 -0000
"Ian Hulin" <address@hidden> wrote in message
OK, here's the question, what's better for our
development/bug-tracking/project management process - add a new
tracker for each of the two modules and mark them as blocking 1686, or
put up patch-sets for each of these as part of Issue 1686, and then
when they've been reviewed, counted down and pushed, put up the final
changes to lily.scm and main.cc, and when this one is reviewed,
counted down and pushed, then we can verify the issue.
By the way, the criteria for verifying all of these patches is that
they do no harm when running the LilyPond regression tests using Guile
I've recently started an aversion to multiple issues. The problem is that
it's a Bug Squad role to mark them as verified and we're now over-run with
issues just tracking patches. As usual, I'm sure Graham won't agree with
me, but I think Squadders should actually check that the patch works if we
mark the issue as verified. Lots of issues - lots of checking. My personal
preference would be to keep the single issue, with multiple patches.
If not this, there should be clear instructions at the top of the issue on
how to verify. "Is 1686 verified? Then verify this one."
Re: Tracker 1686 - Process question - separate Tracker Issues or handle patches as part of T1686?, David Kastrup, 2011/11/08