Hello, You might wonder what I'm doing with jira. I'm trying to get a handle on - what's actively being worked on - what's backlog material - what's dead weight and clear that out
I have always found it hard to find issues in the james jira, even the issues matthieu and I were actively working on in the james jira. I have read the (completely off topic) discussion on jira as issue tracker versus jira as project management tool in the dedicated pg backend jira <https://issues.apache.org/jira/browse/JAMES-2586> and will not close unresolved issues except for really outdated bugs or bugs that are lacking reproduction information. To go about this, I created a kanban board <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=612&view=detail&selectedIssue=JAMES-1403> in the james server project, using the default configuration which creates a fastlane for blocker level bugs. This surfaced 6 bugs (4 of which have now been closed), 2 issues remain that still seem relevant - https://issues.apache.org/jira/browse/JAMES-3580 - https://issues.apache.org/jira/browse/JAMES-3969 I then started reviewing the top issues in the everything else lane. This led me to close very old bugs opened against very old versions since I don't see anyone backporting fixes that far. There are still quite a few left 😢 I also noticed some wish issues, I filtered them out of the board and intend to setup a backlog board with only the wishes. That leaves - improvement requests such as https://issues.apache.org/jira/browse/JAMES-1409 i have no idea if they are actually relevant at the moment. - bugs that sound more like wishes https://issues.apache.org/jira/browse/JAMES-1405 - new features that sound interesting and include years old patches that probably wouldn't apply anymore https://issues.apache.org/jira/browse/JAMES-1357 I'll continue to review the ~300 issues that are left open on my own time. Don't hesitate to tell me if I'm overstepping here and I'll reopen the issues I closed. jean
