-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe migration paths 2.9.2 <-> 3.8.2 <-> 4.3.1 <-> 5.0 #227
Comments
JabRef is not backwards compatible! And we lack resources to maintain other versions. |
We changed the formatting of the bibtex file multiple times. (align on |
I would say, JabRef is backwards compatible (can read old .bib files), but not forward-compatible (old version cannot read bibtex files containing certain JabRef fields) |
Issue to be investigated: No user info about changing bib-format in 4.0 · Issue #3251 · JabRef/jabref |
I think this would have make sense for 4.3.1 <-> 5.0, but it's a bit late for this. Thus, I'll close this issue. We should have this in mind for the next releases though. |
I reopen it, because Debian is still 3.8.2 with 2.000 installations. |
JabRef changed the format of groups (and maybe more) during its releases. It should be written, what the differences in the bibtex files are and how on can go back and froth from 2.9.2, 3.8.2 (latest release in debian), 4.3.1 (latest published release), 5.0 alpha.
For instance, users report:
Maybe, code of JabRef has to be adapted. Maybe, we need to update the 3.8.2 version (or even the 2.9.2 version).
Refs JabRef/jabref#1495
JabRef 3.8.1, 2.9.2 are used in the wild: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895440#44
The text was updated successfully, but these errors were encountered: