Re: Spring cleanup JIRA

2018-03-08 Thread Michael Osipov
Am 2018-03-07 um 23:31 schrieb Michael Osipov: 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 litt

Re: Spring cleanup JIRA

2018-03-08 Thread Robert Scholte
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-clo

Re: Spring cleanup JIRA

2018-03-08 Thread Martijn Verburg
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 wrote: > +1 for the same process as last time. > > /Anders > > On Wed, Mar 7,

Re: Spring cleanup JIRA

2018-03-07 Thread Anders Hammar
+1 for the same process as last time. /Anders On Wed, Mar 7, 2018 at 11:31 PM, Michael Osipov 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 autoclose

Spring cleanup JIRA

2018-03-07 Thread Michael Osipov
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'