DSpace 7.0 is under active development, and is tentatively scheduled to be released in late 2016.
Table of Contents:
Wishlist for DSpace 7.0
The following is an (unordered) list of changes / new features that we'd like to see added to DSpace 6.0. If you have additional features to add, please feel free. We also NEED volunteers to make these features happen, so please do volunteer if you are willing to work on a particular change! Please note that we reserve the right to reschedule/reject any feature that may not align well with the longer term RoadMap.
|Feature||Notes / Tickets||Priority||Volunteer(s)|
|Single Embargo system||Medium|
|Single built-in Statistical Engine (SOLR Statistics)||Low|
|DSpace needs local object identifiers||UUIDs are provided as part of the Service Based API refactor (see above)||Medium||Mark H. Wood|
|Enhance DSpace testing framework |
|Enhanced Solr Statistical Reports||Medium|
|Enhancing Item Level Versioning|
There was some discussion about the Item Level Versioning since it was introduced. This let to disable it by default ( - DS-1388Getting issue details... STATUS ). The discussion went on and we finally have PRs waiting for review and merge regarding the following tickets:
|Make configurable which PI to show in JSPUI item view||Low||Pascal-Nicolas Becker|
|Import of ScienceDirect metadata including embargo and linking to or embedding of the final version||- DS-2877Getting issue details... STATUS||Letitia Mukherjee|
|Oauth authentication plugin||Dryad (a fork of DSpace) has already implemented this, and reportedly is interested in contributing it to DSpace 6||High|
|REST API needs versioning||- DS-2619Getting issue details... STATUS||Peter Dietz|
Pull Requests to review for possible inclusion
New features in DSpace 7.0
New Features in 7.0
General Improvements in 7.0
Bug Fixes in 7.0
Instead of a single "Release Coordinator", the DSpace 7.0 release will be managed by a "Release Team".
Release Team Leader
Release Team Members
Please volunteer (by emailing Tim Donohue), if you are interested in joining the team!
Timeline and Processing
Your contributions are welcome now! Code and documentation need not be finished, so long as it is working and we can all see what it is for. Time is set aside for fixing, polishing, and integration. We have some general Code Contribution Guidelines available, but you are also welcome to ask questions on the dspace-devel mailing list.
Please note that the dates below are estimates of when particular activities may occur. As there are many factors involved in a major release, these are subject to change.
|Date||Milestone||What it means|
|October 06||Deadline for feature pull requests||If you wish to contribute features to DSpace 5.0, you must submit a pull request by this date.|
|October 08||Weekly developers' meeting devoted to review of feature pull requests for 5.0||The entire hour's meeting will be used to discuss proposed features submitted by the deadline.|
|October 15||Weekly developers' meeting devoted to review of feature pull requests for 5.0||The entire hour's meeting will be used to discuss proposed features submitted by the deadline.|
|October 31||Feature freeze||DSpace 5.0 is considered feature-complete on this date. Only bugfixes will be pulled between this date and final release.|
|November 6||Release Candidate 1 tagged||A DSpace 5.0 Release Candidate will be available for wider testing.|
|November 10||Release Candidate 2 tagged||5.0-rc2 was released to address missing optional artifacts from 5.0-rc1 (Mirage2 and LNI)|
|November 10-21||Testathon||Intensive public testing of the 5.0 Release Candidate is invited. The Release Team will focus on getting problems resolved.|
|December 19||Release Candidate 3 tagged||An updated DSpace 5.0 Release Candidate will be available for wider testing.|
|January 15||DSpace 5.0 is publicly released||DSpace 5.0 is released for download and general use.|
Release Process needs to proceed according to the following Maven release process: Release Procedure