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 <[email protected]> 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 <[email protected]>
> 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
>> <[email protected]> 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 <[email protected]>
>> 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: [email protected]
>> > > For additional commands, e-mail: [email protected]
>> > >
>> >
>> >
>> > --
>> > Elliotte Rusty Harold
>> > [email protected]
>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> [email protected]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to