If our current process is leading to people spinning their wheels
unproductively (and I've heard others voice the same concerns that Bryan
is bringing up here), then we need to take that seriously and do
something to fix it.
Bryan Stearns wrote:
This will snowball us back into the situation we're in now. Therefore,
I'm proposing that a change to the policy for situations like this is
necessary, and further, that the policy should be what I said in my last
message: when the tinderbox is yellow for an extended period of time
(and I think the current situation qualifies: it hasn't been green
across the board in the eight days!), we *close the tree* and declare a
switch to this policy:
> - P1 bugs get filed for each failure
> - The failing tests get disabled on the platforms on which they fail
> (with bug numbers in the comments)
> - People are assigned to fix those bugs and reenable the tests.
This sounds like a perfectly reasonable proposal to me.
I know many of you are focused on hitting the feature freeze deadline;
in the long run it will be worth the investment to stabilize the tests.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
