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 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: 
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!


Note: if you see an issue which worth keeping, just add a comment to the 
issue: "still valid"


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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-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  
 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  wrote:


+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 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: 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: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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, 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 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: 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: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

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 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: 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: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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't get shorter and a lot of them do 
not even contain a sample project.


JIRA query: 
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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org