Hervé, Am 2015-12-25 um 17:41 schrieb [email protected]:
this is a *bug report* squash, not a bug squash
correct, my bad. That was a misunderstanding on my side.
And looking at the list, I see not only bug reports but a good number of enhancements notes (TODO list): perhaps limiting the search to bugs only would avoid dropping our TODO list
I agree but do you think that you will ever address them in the near future even if haven't done in the last couple of years? I do even close my own issues because I know I won't implement them. The best would be you'd add a validity note to your tickets, they will get bumped and excluded by default.
And this notice IMHO should go to maven-users too
I will prepare an email to both lists will a drilled down amount of issues with types and give people at least a week to react too.
Is that acceptable for you? Michael
----- Mail original ----- De: "Michael Osipov" <[email protected]> À: [email protected] Envoyé: Vendredi 25 Décembre 2015 00:05:55 Objet: Another yearly bug squash Hi folks, I'd like to do another bug squash like a did last year. We currently have 132 unresolved bugs which haven't been updated for more than three years. I hardly believe that they will be updated ever. Maybe they have been resolved with new versions automatically. Anyway, here is the query for: category = Maven AND updated <= -156w AND resolution = Unresolved ORDER BY created DESC Please have a look whether you see some of yours which are still valid or anything else. If you don't object, I will go ahead and close them as won't fix. Let me know by the end of the week.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
