This morning I finished reviewing the last of these issues. Only four remain untouched, all of which were previously autoclosed and reopened, so we shouldn't autoclose them again.
I didn't keep track of exact numbers of how many I closed, reprioritized, duped, marked abandoned etc. There were a number of issues that had long comment threads related to proposed fixes and changes, indicating that a lot of work and thought had gone into them but ultimately didn't lead anywhere. In these cases, I tried to make my best judgement based on the thread as to whether the issue deserved to stay open or not. Since everything in the list was already scheduled for closure, I was more aggressive than usual about "Won't Fixing" and closing issues. If any seem to you to be closed in error, you're probably right. Please reopen them. There were a lot of new feature requests that were incomplete and hard to follow. There were also many patches submitted by non-committers that had never been reviewed. We might want to rethink how we accept new feature and model change requests. Filing such a request in Jira seems likely to lead to a frustrating experience for contributors and reviewers alike. Perhaps we can ask for more formal design proposals in a doc outside of Jira that is discussed on the dev mailing list first before it gets added to the Jira and reserve Jira only for new features we actively want to do. I'm not sure. But I would prefer not to be back in this place five years from now. On Fri, Dec 20, 2019 at 7:14 AM Tibor Digana <tibordig...@apache.org> wrote: > > sorry for typo, in the backlog they should not be closed because they are > serious bugs and need to be fixed. > > On Fri, Dec 20, 2019 at 1:11 PM Tibor Digana <tibordig...@apache.org> wrote: > > > I want to review the closed issues as well i would like to come up with > > those which should be reopened to a certain release version. > > I guess the release version should be set in such case. > > We have also backlog version and that's the place where the issues should > > be closed be the version has not been proposed yet. > > > > On Fri, Dec 20, 2019 at 12:49 PM Elliotte Rusty Harold <elh...@ibiblio.org> > > wrote: > > > >> One thing we should try going forward is be more ready to won't fix > >> and close bugs and RFEs we disagree with. I've seen several examples > >> where the comments indicate the maintainers did not agree with the > >> issue, but it still wasn't closed. E.g. > >> > >> https://issues.apache.org/jira/browse/SUREFIRE-1227 > >> > >> Closing an issue is not irrevocable. Issues can always be reopened, if > >> the reporter or anyone else disagrees. Indeed it is more respectful to > >> reporters to be politely honest with them about our true objections, > >> rather than simply ignoring the issue and not responding. > >> > >> On Fri, Dec 20, 2019 at 6:29 AM Elliotte Rusty Harold > >> <elh...@ibiblio.org> wrote: > >> > > >> > 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 > >> > >> > >> > >> -- > >> 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 > >> > >> -- 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
