Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
This page tracks the scope and progress of the upcoming DSpace 6.4 release.
If you know of an open JIRA issue or contribution that you really want to see make it into 6.4 that isn't listed on this page, you can give it some attention by posting a message to the DSpace Developer mailing list, and/or giving it a shout-out in the #dev channel in the DSpace Slack
If you're able to volunteer time to code up a solution related to a JIRA issue that needs a volunteer, send in that Pull Request against the dspace-6_x branch!
If you're able to review and test an open Pull Request to help get it approved and merged, please do try out some PRs currently waiting for reviews and give your comments / results to help us keep things moving.
Please remember to forward port accepted PRs to 7.0 (master), where applicable
Any non-JSPUI and non-XMLUI bug fixes should be ported to the "master" branch to ensure they remain fixed in 7.0. This includes any fixes to the Java API, OAI-PMH, REST API (as it's deprecated but still included in 7.0), SWORD (v1 or v2) or RDF. Any forward-port PRs can merged quickly, provided that the original PR was accepted/merged for 6.4, one reviewer approves & all tests pass in Travis CI. If there are any questions, or you need a quick review on a forward-port PR, contact Tim Donohue.
Scope and plan
DSpace 6.3 was released on June 2018. A new minor release for 6.x (and 5.x, 4.x) is really needed to help keep the community up to date with bug fixes and improvements.
Though there are many open PRs and issues against 6.x or flagged for 6.4, it is likely that only a critical subsection of these PRs will be included in 6.4 by <deadline> to ensure timely release. Many Dspace developers and committers are busy with the DSpace 7.0 release and can't divert too much energy to 6.4, so the release process will have to be fairly lean.
Release team volunteers (put a hand up if you want to help!):
Hrafn Malmquist - (especially interested in REST API fixe (DS-4065, see PR 2275) and various Discovery fixes, for instance DS-3637)
Luigi Andrea Pascarelli (4Science) - (high interest in having DS-4149 OpenAIRE literature v4 and DS-2715 ORCID support for JSPUI included in the release)
Tentative cut-off for PR merging:
May 1 2020
Suggested pre-release application (usability, functional) tests for DSpace 6.4
The below cover most of the fixes and improvements in DSpace 6.4. If we can get volunteers pooled / assigned so that a couple of people are thoroughly testing each of the below functional areas, that'll help confidence in release stability and in catching any last minute problems:
- (TODO, complete this list after review of PRs)
Approved PRs that just need merging
These PRs are flagged for 6.4 and already have approval. They should be reviewed again and either merged (& ported to master branch where applicable) or rescheduled (if for some reason the approval is not enough to get them into 6.4).
Issues / PRs for special attention (easy wins or "just one more +1!"), and larger changes that need testers
| Issue | PR(s) | Category | Notes |
|---|---|---|---|
PR#2693 (6.x) PR#2692 (master) | Bigger change | Adding an 'Anonymize Statistics' feature to DSpace for GDPR compliance. Most of the discussion is on JIRA and on the master PR #2692. Consensus so far is that it works well, is definitely worth trying to get into 6.4, but could do with a bit more testing just to ensure no data loss to stats docs can occur in various conditions (see last master comment) | |
PR#2710 PR#2704 (5.x port) | Bigger change | Adding ORCIDv2 authority control support to JSPUI NOTE: include fix also for | |
| PR#2191 PR#2113 PR#1730 (merged) PR#2464 | Competing PRs | A small bugfix, but there seem to be three PRs with similar solutions. |
Issues merged for 6.4, waiting on something else (eg. porting to other another version, or documentation)
These issues are already fixed in 6.x branch but cannot be closed until they are forward-ported to master, or in the case of a security / critical bugfix, backported to 4.x and 5.x.
| Issue | Notes | Further work needed |
|---|---|---|
| Already merged for 6.x but master Travis CI build has Unit Test errors which need fixing | port to master (5.x PR also exists) | |
| Already merged for 6.x but master PR#2121 has conflicts - very simple conflict involving whitespace in the imports, by the looks... | port to master | |
| Already merged for both fix versions but needs 6.x documentation (7.0 doc already added) just before 6.4 release | documentation (new feature) | |
| Already merged for all fix versions but ones one additional round of small fixes, incorrect date name | tiny change to 3 branches | |
| Already merged for 6.x but waiting on master port (which is implemented quite differently, at API level) | port to master |
TODO
Do we need the full "first review, second review, test, merge, port" checklist here? Depends how our workload looks. Certainly if there are PRs people are lobbying for, a list might help. (see 6.3 equiv checklist DSpace Release 6.3 Status)
Open PRs flagged for 6.4 milestone (Github):
https://github.com/DSpace/DSpace/pulls?q=is%3Aopen+is%3Apr+milestone%3A6.4
Non-closed JIRA Issues with 6.4 milestones:
Fixed for 6.4:
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license
, unless otherwise noted.