While working through the bugs I found this interesting bit of history: https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like we've been here before. Some of the bugs that were autoclosed then were reopened and are now scheduled for autoclose again. Any thoughts about how we might update our processes to avoid getting into this situation again? On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <micha...@apache.org> wrote: > > Hi folks, > > after at least one year of silence, I'd like to perform another JIRA > issue cleanup for issues which have been not touched for more than three > years. > > Query: > https://issues.apache.org/jira/issues/?filter=12333204&jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC > > Stats: > > 567 issues not touched for more than three years > of which > * 68 have fix version set > * 36 were already reopened, should they be excluded? > * 1 in progress by Karl > > Type breakdown: > * 200 bugs > * 164 improvements > * 72 new features > * 6 subtasks > * 13 tasks > * 12 wishes > > If there are issues still valid for you please leave a comment on the > issue and they will not appear in the query anymore. > Please also raise your voice if you have anything to discuss. > > If the issue is not modified or no objection has been raised, I will > autoclose those issues with a comment by 2019-12-30. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
