Re: Spring cleanup JIRA

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Spring cleanup JIRA

karianna
Non binding but agreed - once an issue list gets beyond 50 it's hard to see
the forest, once it's beyond 100 you can pretty much guarantee that
everyone is lost.

Cheers,
Martijn

On 8 March 2018 at 07:45, Anders Hammar <[hidden email]> wrote:

> +1 for the same process as last time.
>
> /Anders
>
> On Wed, Mar 7, 2018 at 11:31 PM, Michael Osipov <[hidden email]>
> wrote:
>
> > Folks,
> >
> > I did yet another analysis on open issues. We have currently more than
> 400
> > open issues which haven't been touched for more than three (3) years.
> >
> > The last two times I autoclosed them with a message. People could request
> > a reopen, very little did.
> >
> > Should we do this again? The list won't get shorter and a lot of them do
> > not even contain a sample project.
> >
> > JIRA query: <a href="https://issues.apache.org/jira/issues/?jql=category%20%3D%">https://issues.apache.org/jira/issues/?jql=category%20%3D%
> > 20Maven%20AND%20updated%20%3C%3D%20-156w%20AND%20resolution%
> > 20%3D%20Unresolved%20ORDER%20BY%20created%20DESC
> >
> > Please comment!
> >
> > Michael
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Spring cleanup JIRA

rfscholte
100 for the whole Maven project? Luckily we have ~85 projects, so the  
damage looks manageable.
However, with a total of 2000+ open issues and with the current active  
resources it is impossible to fix them all.
So yes, close them as Auto-Close with a clear message. I sometimes look at  
auto-closed issues, sometimes  they are indeed interesting to add even  
though the reporter didn't ask to reopen such issue.

thanks,
Robert

[1]  
https://cwiki.apache.org/confluence/display/MAVEN/Maven+JIRA+issues+overview


On Thu, 08 Mar 2018 11:16:57 +0100, Martijn Verburg  
<[hidden email]> wrote:

> Non binding but agreed - once an issue list gets beyond 50 it's hard to  
> see
> the forest, once it's beyond 100 you can pretty much guarantee that
> everyone is lost.
>
> Cheers,
> Martijn
>
> On 8 March 2018 at 07:45, Anders Hammar <[hidden email]> wrote:
>
>> +1 for the same process as last time.
>>
>> /Anders
>>
>> On Wed, Mar 7, 2018 at 11:31 PM, Michael Osipov <[hidden email]>
>> wrote:
>>
>> > Folks,
>> >
>> > I did yet another analysis on open issues. We have currently more than
>> 400
>> > open issues which haven't been touched for more than three (3) years.
>> >
>> > The last two times I autoclosed them with a message. People could  
>> request
>> > a reopen, very little did.
>> >
>> > Should we do this again? The list won't get shorter and a lot of them  
>> do
>> > not even contain a sample project.
>> >
>> > JIRA query: <a href="https://issues.apache.org/jira/issues/?jql=category%20%3D%">https://issues.apache.org/jira/issues/?jql=category%20%3D%
>> > 20Maven%20AND%20updated%20%3C%3D%20-156w%20AND%20resolution%
>> > 20%3D%20Unresolved%20ORDER%20BY%20created%20DESC
>> >
>> > Please comment!
>> >
>> > 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]