JabRef development: best way to file all those small issues for upcoming milestones?

(Rainhard Findling) #1

Seems I am filing a lot of issues recently that have to do with features that are available in the old version (JabRef 4.3 atm) and which seem to be missing/broken/different in master, which is heading for the next milestone (4.4/5.0 atm).

I am aware that you collect issues that you want to fix for the next milestones in https://github.com/JabRef/jabref/milestone. However, there seems to be only few issues there atm - I guess there would be way more of them it all would be filed, especially for 5.0.

So what is the best way to file all those small issues (potentially also feature requests) that are still missing in master, seem broken, where docs are out of sync, etc? Do you guys prefer me to open an issue for every detail that seems to be somewhat broken in master, compared to what is there in 4.3? I ask as I want to help - and not annoy guys :smiley:
Thx!

(Tobias Diez) #2

We are also using the github project feature to keep track of what has to be done for the next release: https://github.com/JabRef/jabref/projects/2.

It would be of great help if you (and others) report all these small little bugs that are still present. In this way, we developers can focus on fixing these bugs instead of spending the time to search for them in the first place. Note, however, that some features were altered and/or removed on purpose. Thus, it is best to check the changelog before you submit an issue. The documentation is currently lagging behind and is sometimes out-of-date. In this cases, you can submit an issue to https://github.com/JabRef/help.jabref.org or even better update the help files on your own (click the small pencil icon in github).

Thanks for your help!

(Rainhard Findling) #3

OK, I’ll check those before filing bugs. I don’t have much time to spend on this myself, but quickly reporting things should always work :slight_smile:

(Christoph) #4

Hi,

see also here for a list of active/possible bug or the label bug.