Hello Jean!
Thanks a lot for the initiative.
I and Eugen had been doing that several time in the last few years,
though I agree the JIRA backlog is still messy.
Answers inlined.
Best regards
On 30/08/2024 09:42, Jean Helou wrote:
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>
Thanks!
I had a lok and did triage a couple of tickets...
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
3.6.0 is old now, unsure it is still relevant on newer versions of james
-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.
This one likely is: this field takes a coma separated list of address,
stored in a string field of size 100...
A good example of limitations that make me claim JPA implementation
isn't great ;-)
(thanks for pointing this out!)
And clearly it is not an improvment but clearly a *bug*!
- bugs that sound more like wishes
https://issues.apache.org/jira/browse/JAMES-1405
log4j specific and old. I would disregard it.
Agreed it is a wish ...
- 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.
+1 you are doing a great job, I'll try to keep up with it!
jean
