[
http://jira.codehaus.org/browse/MPA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98717
]
Jason van Zyl commented on MPA-90:
----------------------------------
Of primarily importance is getting some meaning back. There are close to 800
open issues which is totally out of control.
Some things that can be done are:
- looking for duplicates within components (not to say there are duplicates in
other components)
- close as incomplete any bug report that doesn't have a sample project (we
just can't reproduce the problem without it and people can reopen them)
- An incoming bucket that we know has not been looked at (is there a way to do
this easily? Or should we do what JetBrains does and create a separate project
from which to select?)
- look for issues that have been assigned to the wrong project
I think we need to take a heavy hand to push the open issue count down. And
provide a better means for processing them. Even if we close many and ask
people to make working projects for testing.
> Clean up JIRA
> -------------
>
> Key: MPA-90
> URL: http://jira.codehaus.org/browse/MPA-90
> Project: Maven Project Administration
> Issue Type: Task
> Components: Issue Management
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: Maven 2.1 Prep
>
>
> # Flush out the duplicates
> # Close what issues have been dealt with
> # Delete the issues with incomprehensible explanations
> # Set appropriate components
> # Set appropriate versions
> Currently need a way to attack this, unless it's just one person going
> through them all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
