We decided that our JIRA  situation for the core Maven project is out of control. With over 700 open issues spanning 12 years it has become impossible to keep track of anything properly, making it hard to manage the project. We want to curate JIRA better, but to get there we need to do a mass closing of issues and try to whittle it down to a set that's manageable. We realize it's our own fault for not taking better care and that people have invested time in submitting issues, but in order to get things back on track, we have decided to close out all issues that have not been updated in the last year, without an assignee.

Now if you feel strongly about an issue then feel free to reopen the the issue, but we are going to be a more strict about what is deemed a valid issue submission. If you are submitting a bug report, then you have to provide a stand-alone project that we can use to reproduce the problem. We are not going to checkout your OSS project and try to build it, and we're not going to try and decipher a long message and interpret what you mean, and if it happens in your production build that you can't share, then there's not really much we can do about it unless you can separate out the issue. Without a stand-alone project to demonstrate the problem, it's just too time consuming to try and figure out. We have generally done the work to create an integration test for changes, and that is very time consuming in itself. If an issue comes in without an example project to demonstrate the problem, then after 3 months it will be closed. The fastest way to get your issue resolved is by making it dead simple for us to run and project and see the problem.

We're trying to get the project back on track and this is one of the things we need to do. We'll curate JIRA better from now on. We now still (as of January 22nd) have ~220 issues to go through and we'll try and get through those as fast as we can.

Thanks for your patience,

The Maven Team

  • No labels