>>> * we need to go through all RESOLVED LATER tickets, reopen them by >>> setting appropriate values (lowest priority, upstream), and >>> explain why (pointing to this thread). Help welcome. >> >> Since free time is a luxury, what about simply a bulk change TO NEW / >> LOWEST. I know it's not a perfect solution, but is a big improvement done >> fast. Then active teams and contributors (many of them receiving >> notifications for the changes) will fine tune each one of them. Or not, but >> this would mean that such reports would have been ignored anyway in your >> eventual call for volunteers. >> >I think somebody (or possibly a few somebodies with knowledge of >different parts of the code) should at least quickly scan these lists, >since some of the things marked as LATER might have been fixed in the >meantime (and nobody found the bug to close, since it was RESOLVED) or >have been made irrelevant (such as >https://bugzilla.wikimedia.org/show_bug.cgi?id=34329 which I found >skimming the list a few days ago).
A week provides ample time to do that. Although, I'm sure if there are disagreements on that length of time, another could easily be decided upon. Thank you, Derric Atzrott _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
