Re: Yearly JIRA cleanup

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
Please don't. There are certainly some real and important issues in
there. More importantly, users spent a great deal of effort and time
to file those. Bulk closing them tells those users we don't value
their feedback or effort. It is useful to triage these issues and
consider them individually. Doubtless many of these issues are already
fixed, moot, or things we expressly chose not to do. However this
should be decided case by case. We can't simply close our eyes and
pretend they're all irrelevant.

On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

michaelo
Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> Please don't. There are certainly some real and important issues in
> there. More importantly, users spent a great deal of effort and time
> to file those. Bulk closing them tells those users we don't value
> their feedback or effort. It is useful to triage these issues and
> consider them individually. Doubtless many of these issues are already
> fixed, moot, or things we expressly chose not to do. However this
> should be decided case by case. We can't simply close our eyes and
> pretend they're all irrelevant.

Hi Elliotte,

I share your concerns. I do traverse through tickets once in a while and
check for samples projects. Please also feel free to go through the list
and update them.
At the end we need to be honest. I.e., if we weren't to triage them
within three years, we likely never won't. We honestly tell that we
acknowledge the issue, but are simply unable to do anything fruitful.

We have almost 2000 open issues. How would you reasonably sieve between
them? even if you allocate 10 min per ticket, you would need two months
of work to triage them.

Regards,

Michael

> On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <[hidden email]> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

michaelo
In reply to this post by Elliotte Rusty Harold
Take your time, you have at least three weeks.

Am 2019-12-08 um 18:23 schrieb Tibor Digana:

> Hi Michael,
>
> What's up :-)
> Thx for making the list of issues.
> Pls give me one day to see it completely. I will get back to you tomorrow.
>
> Cheers
> Tibor17
>
> On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty Harold <[hidden email]>
> wrote:
>
>> Please don't. There are certainly some real and important issues in
>> there. More importantly, users spent a great deal of effort and time
>> to file those. Bulk closing them tells those users we don't value
>> their feedback or effort. It is useful to triage these issues and
>> consider them individually. Doubtless many of these issues are already
>> fixed, moot, or things we expressly chose not to do. However this
>> should be decided case by case. We can't simply close our eyes and
>> pretend they're all irrelevant.
>>
>> On Sun, Dec 8, 2019 at 7:50 AM Michael Osipov <[hidden email]> 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: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> [hidden email]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
In reply to this post by michaelo
On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov <[hidden email]> wrote:

>
> Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > Please don't. There are certainly some real and important issues in
> > there. More importantly, users spent a great deal of effort and time
> > to file those. Bulk closing them tells those users we don't value
> > their feedback or effort. It is useful to triage these issues and
> > consider them individually. Doubtless many of these issues are already
> > fixed, moot, or things we expressly chose not to do. However this
> > should be decided case by case. We can't simply close our eyes and
> > pretend they're all irrelevant.
>
> Hi Elliotte,

> We have almost 2000 open issues. How would you reasonably sieve between
> them? even if you allocate 10 min per ticket, you would need two months
> of work to triage them.
>

Use the time we have to fix as much as we can. Leave the rest open.
Some will never be touched but some will be when someone encounters
the same problem and finds the bug again. It's better to leave it open
and unaddressed than to close it without giving it a fair look.

As to time spent triaging, it's worth considering whether permissions
could be opened up further. Right now, almost anyone can file a bug
but few people can resolve and close them. I can't, for example, even
when I see one that's clearly no longer relevant. :-(

--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

stephenconnolly
On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold <[hidden email]>
wrote:

> On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov <[hidden email]> wrote:
> >
> > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > > Please don't. There are certainly some real and important issues in
> > > there. More importantly, users spent a great deal of effort and time
> > > to file those. Bulk closing them tells those users we don't value
> > > their feedback or effort. It is useful to triage these issues and
> > > consider them individually. Doubtless many of these issues are already
> > > fixed, moot, or things we expressly chose not to do. However this
> > > should be decided case by case. We can't simply close our eyes and
> > > pretend they're all irrelevant.
> >
> > Hi Elliotte,
>
> > We have almost 2000 open issues. How would you reasonably sieve between
> > them? even if you allocate 10 min per ticket, you would need two months
> > of work to triage them.
> >
>
> Use the time we have to fix as much as we can. Leave the rest open.
> Some will never be touched but some will be when someone encounters
> the same problem and finds the bug again. It's better to leave it open
> and unaddressed than to close it without giving it a fair look.
>
> As to time spent triaging, it's worth considering whether permissions
> could be opened up further. Right now, almost anyone can file a bug
> but few people can resolve and close them. I can't, for example, even
> when I see one that's clearly no longer relevant. :-(


As soon as Brian fixes your JIRA permissions you’ll be able too... your
committer status is only freshly minted! (welcome/congrats)

Another issue is the lack of a clearly defined process for triage. We
should document what we mean by triage and what outcomes we expect. That
could even include closing stale issues after a check for active reporters

>
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Sent from my phone
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

rfscholte
IIUC since Jira uses the ASF LDAP, there's no extra need for Brian to do this anymore. All should be in place by now.

thanks,
Robert
On 12-12-2019 15:20:24, Stephen Connolly <[hidden email]> wrote:
On Mon 9 Dec 2019 at 20:53, Elliotte Rusty Harold
wrote:

> On Mon, Dec 9, 2019 at 3:18 PM Michael Osipov wrote:
> >
> > Am 2019-12-08 um 18:08 schrieb Elliotte Rusty Harold:
> > > Please don't. There are certainly some real and important issues in
> > > there. More importantly, users spent a great deal of effort and time
> > > to file those. Bulk closing them tells those users we don't value
> > > their feedback or effort. It is useful to triage these issues and
> > > consider them individually. Doubtless many of these issues are already
> > > fixed, moot, or things we expressly chose not to do. However this
> > > should be decided case by case. We can't simply close our eyes and
> > > pretend they're all irrelevant.
> >
> > Hi Elliotte,
>
> > We have almost 2000 open issues. How would you reasonably sieve between
> > them? even if you allocate 10 min per ticket, you would need two months
> > of work to triage them.
> >
>
> Use the time we have to fix as much as we can. Leave the rest open.
> Some will never be touched but some will be when someone encounters
> the same problem and finds the bug again. It's better to leave it open
> and unaddressed than to close it without giving it a fair look.
>
> As to time spent triaging, it's worth considering whether permissions
> could be opened up further. Right now, almost anyone can file a bug
> but few people can resolve and close them. I can't, for example, even
> when I see one that's clearly no longer relevant. :-(


As soon as Brian fixes your JIRA permissions you’ll be able too... your
committer status is only freshly minted! (welcome/congrats)

Another issue is the lack of a clearly defined process for triage. We
should document what we mean by triage and what outcomes we expect. That
could even include closing stale issues after a check for active reporters

>
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Sent from my phone
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

michaelo
Am 2019-12-13 um 16:08 schrieb Elliotte Rusty Harold:
> NVM, I seem to have access now. I think I just needed to logout with
> my old credentials and back in with the new ones.

Elliotte,

please go through the list and update those tickets you seen to be
addressible within a decent timeframe.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
In reply to this post by Elliotte Rusty Harold
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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

michaelo
I will exlude those. It does not makes sense to close/reopen again.

Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold:

> 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 <[hidden email]> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Elliotte Rusty Harold
Please share the new query for this. It would give me fewer issues to look at.

By the way, I've chopped the original list from over four hundred to
just over two hundred, learned a lot about Maven in the process, found
one or two gems that have serious impact at my day job, and identified
one truly scary security issue someone badly needs to look at.

On Fri, Dec 20, 2019 at 6:42 AM Michael Osipov <[hidden email]> wrote:

>
> I will exlude those. It does not makes sense to close/reopen again.
>
> Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold:
> > 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 <[hidden email]> 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: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> >
>


--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Tibor Digana
In reply to this post by Elliotte Rusty Harold
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 <[hidden email]>
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
> <[hidden email]> 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 <[hidden email]>
> 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: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> >
> >
> > --
> > Elliotte Rusty Harold
> > [hidden email]
>
>
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

Tibor Digana
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 <[hidden email]> 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 <[hidden email]>
> 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
>> <[hidden email]> 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 <[hidden email]>
>> 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: [hidden email]
>> > > For additional commands, e-mail: [hidden email]
>> > >
>> >
>> >
>> > --
>> > Elliotte Rusty Harold
>> > [hidden email]
>>
>>
>>
>> --
>> Elliotte Rusty Harold
>> [hidden email]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: Yearly JIRA cleanup

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



--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]