I'm noticing that a lot of the RESO LATE bugs are requests for extensions or site requests which either: 1) We aren't currently installing that extension (Ok for these to be RESO LATE) 2) The original requester needs to provide further information
Do we want that second category to be resolved later? If so, we're going to be waiting a long time for people to come back with more details. Should bugs that are resolved later because the original requester or someone else needs to provide more info instead be closed invalid, or something else?
-- Dan Collins
On Tue, Nov 29, 2011 at 4:00 PM, Jay Ashworth jra@baylink.com wrote:
----- Original Message -----
From: "Diederik van Liere" dvanliere@gmail.com
The question is, when is LATER? Technically, these bugs are not open and so nobody will ever see them again and that's how they will be forgotten.
I would assume that "LATER" is, in a release after this one... and that the proper solution is to do as you suggest (stripe them back to NEW) *after the next release is cut*.
Anyone think that's a bad idea?
Do we have a "Target release" in our BZ?
Cheers,
-- jra
Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l