Table of Contents:
Priorities for 8.0
The following is an (unordered) list of new features that the DSpace Steering Group would like to see added to the DSpace 8.0 release. The overarching goal is to keep the 8.0 release smaller in size (in terms of new features), and find ways to help the community more easily upgrade to 7.x or 8.x. See also RoadMap.
|Feature(s)||Notes / Tickets||Priority||Volunteer(s)|
|COAR Notify support||High||4Science and Harvard University|
|Correction service to enhance data quality (via OpenAIRE Graph)||High||4Science|
|Migrate "REST-Based Quality Control Reports" to new REST API|
https://github.com/DSpace/DSpace/issues/7641 (see linked PRs)
|High||Université Laval, Canada|
|Duplicate Detection in Submission (ported from DSpace-CRIS)||High||The Library Code|
|Any new features which empower users in the Admin User Interface|
Various tickets, based on volunteers. The exact tickets which will be completed will be based on what volunteers wish to claim for 8.0. Any tickets on the 8.0 board which "empower admins" fall into this category. Get in touch with Tim Donohue if you have questions or wish to volunteer for a ticket.
(Various institutions or volunteers)
|Any features which existed in 6.x but missed the 7.x series of releases|
Various tickets, based on volunteers. Any community volunteer is welcome to "port" any feature that existed in the 6.x XMLUI or JSPUI 6.x to the 8.0 release. Get in touch with Tim Donohue if you have questions or wish to volunteer for a ticket.
|High||(Various institutions or volunteers)|
Tickets & Pull Requests to review for possible inclusion
All potential tickets & pull requests may be found on our 8.0 Project Board.
- 8.0 Project Board: https://github.com/orgs/DSpace/projects/27
If there is a feature you wish to work on which is not on that 8.0 Project Board, please create a GitHub issue ticket to describe it (or find one if it exists) and contact Tim Donohue (via email or Slack) about possible inclusion in 8.0.
Keep in mind, even if a ticket/PR exists on the 8.0 Project Board, that does not guarantee it will be completed in time for 8.0. We'll do our best to get it included, but all development & testing/reviewing is volunteer based. You can help ensure a PR's inclusion by volunteering to help test or review the code! Any work that cannot be achieved in time for 8.0 will be rescheduled.
Updates and discussions will take place in weekly Developer Meetings.
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|
|Friday, January 19, 2024||Deadline for feature pull requests||If you wish to contribute features to DSpace 8.0, you must submit a pull request by this date.|
|Friday, February 9, 2024||Feature PR Review/Test Deadline||Initial reviews/testing of PRs should be completed by all assigned reviewers.|
|Friday, February 23, 2024||Feature PR Merge Deadline (Feature Freeze)||DSpace 8.0 is considered feature-complete on this date. All Feature PRs should be merged. Only bug fixes will be pulled between this date and final release.|
|Friday, March 1, 2014||Release Candidate 1 tagged||A DSpace 8.0 Release Candidate will be available for wider testing.|
|March 4-15, 2024||Testathon||Intensive public testing of the 8.0 Release Candidate is invited. The Release Team will focus on getting problems resolved.|
|Friday, March 29, 2024||Deadline for bug-fix pull requests||Bug fixes should ideally be submitted by this date.|
|Friday, April 12, 2024||Bug-Fix PR Merge Deadline (Code Freeze)||Ideally all bug fixes are merged by this date. Code is "frozen", with exceptions only made if major issues are discovered.|
|April 15-19, 2024||Final Cleanup / Documentation||This week is set aside for any final cleanup (or very late bug fixes) that need to be applied to the code. Also used to finalize Documentation, Release Notes, etc.|
|Monday, April 22, 2024 (tentative)||DSpace 8.0 is publicly released||DSpace 8.0 is released for download and general use.|
Release Process needs to proceed according to the following Maven release process: Release Procedure