[cle-release-team] Close all Task/Resolved/Fixed ?

[Noah Botimer]

I wouldn't say that it's 100%. Feature requests have often turned into Tasks because they're not really bugs. They might represent an important functional or technical change. In a purist's world, there would be a test plan attached to this kind of thing when implemented/"fixed". In reality, that's rarely the case, and our line between Request/Task/Bug also isn't as stark as it might be.

A different scenario to consider is that things like upgrading libraries or adding translations might be under Tasks. Typically, if our library upgrades go badly, there is follow-up work or a bug filed. But I'm not sure we can assume that.

This is the long way of saying -- I don't think that Tasks marked Fixed/Resolved should be closed without at least checking their nature. There may be things to test or comments that indicate testing results.

As with any of this cleanup, a few seconds of human eyes on a ticket is very valuable as far as sorting is concerned. My perspective is that this is an important input channel for QA efforts -- unknown/unexpectedly complete work awaiting testing.

Thanks,
-Noah

On Aug 22, 2012, at 4:59 PM, Neal Caidin wrote:

> Hi All,
> 
> Matt and I were talking about closing Tasks. It sounds like, in theory anyway, that we could close all Tasks that are Resolved and Fixed, because in theory these would not need any testing. Does that sound right?
> 
> We could close about 370 tickets with around 1/3 of those being SAK.  I would leave open the Incomplete and Incorporated, which would need validation, as we discussed for the other issues we've closed.
> 
> Thanks,
> Neal
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team