Obviously priorities for 10.0 depends heavily on a final decision around a potential merger with DSpace-CRIS. In meantime, 10.0 has general priorities similar to DSpace Release 9.0 Status
Are there other features / improvements you'd like to see soon in DSpace?
Other topics
(Please add any here that you'd like to discuss)
Board Review:
9.0 Project Board- Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
Backlog Board- Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
To quickly find PRs assigned to you for review, visit https://github.com/pulls/review-requested (This is also available in the GitHub header under "Pull Requests → Review Requests")
Deadline is TBD for both 8.2 and 7.6.4. Bug fix releases do not have fixed/scheduled deadlines.Instead, the developer team will determine when to create a release based on the significance of the issues to solve. (e.g. If major issues are fixed, then a bug fix release will occur more rapidly. If minor issues are found, then a bug fix release may be delayed until sufficient fixes have been made to warrant a release)
Bug/security fixes only. These minor releases will not include any new features.
New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
Accessibility fixes are also allowed in bug fix releases, provided they don't significantly modify component behavior or similar.
Bug fix PRsshould be created against "main" branch where possible. The "main" branch has the most strict code style rules. (i.e. PRs created against dspace-7_x are becoming more difficult to port forward.)
Per our support policy, bug fixes are only guaranteed to be ported back to 8.x. That said, where possible, we'll try to backport bug fixes (especially significant ones) to 7.6.x.
Keep in mind, if a specific bug fix is important to you in 7.6.x, then it is best to create two PRs (one for main and one for "dspace-7_x"). If you are able to provide a backport version of the PR, then we will merge it alongside the "main" branch version.
NOTE: In many scenarios, a backport to "dspace-8_x" should be possible to automate using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action
Try "Pull Request Trading" for a quicker review
Do you have a PR stuck in "under review" that you really want to see move forward? Or maybe it's someone else's PR but you want to get it more attention?
Open Repositors will be happening June 15-18, 2025
DSpace Developers workshop will happen on June 15; please sign up if you'd like to share your work or suggest a topic for discussion
See DSpace at OR2025 for all DSpace related presentations, workshops, etc. at OR25; slide decks will be gathered on this page for those who cannot attend OR
If you have any questions or notice that something is missing from this list, please feel free to edit the wiki page or reach out to Tim/Holger
9.0 Release
Tim is still working on a final count of contributors, probably in 80-100 range
Release notes are close to being finalized; please look through them to double check them if you (or your client) is recognized correctly
Documentation is in good state; please take a look and double check things (esp. committers)
Acknowledgment section is not yet up to date; backend section still needs to be updated; once this list is fully ready for review, Tim will ping the dev channel on slack; please review this as well
Release will go out either today or tomorrow; announcement will happen next Tuesday (Monday is a national Holiday in the US); Tim will send updates on the dev channel in slack
If there are any other final tasks, please contact Tim as soon as possible
A huge thank you to everyone who has contributed!
Maintenance releases
Even after 9.0 goes out the door, DSpace 7 is still under maintenance
Tim has updated our maintenance board to include 9.x maintenance, has moved over all bug tickets off the old 9.0 board on GitHub (other than things in the "done" category) into the maintenance board; the old 9.0 board will be closed out once the release has been officially completed
There is a new 10.0 board, where all the new features that didn't make 9.0 have been moved to
Please review the boards, esp. the maintenance board, since we want to get maintenance releases out for 8.2 and 7.6.4 relatively soon (after OR); anything in 9.0 flagged to be backported and is still outstanding will be backported into these
There's no deadline for these as of yet, we will set one in the coming weeks
There are some bug fixes on the 9.0 board that have the "port to" label; some have not yet been ported; please take a look to see what hasn't been backported yet
10.0 Release
There is a 10.0 board that has not yet been organized or cleaned up; everything feature related left over from 9.0 is now on that board
There is already a big backlog on the "under review" and "needs reviewer assigned" columns (~130)
A lot of these PRs have been opened for some time
Would be great if we could come up with a strategy, ideas on how to speed up this process; please pass any ideas Tim's way
Steering will be discussing speeding up code reviews in the coming weeks and try to come up with ideas and solutions
If you'd like to see them in 10.0 release, please test these, review these
Some bug tickets found their way on to this board and need to be cleaned up
Tentative plan: have 10.0 out roughly a year after 9.0's release; no date as of yet, but roughly May 2026
10.0 priorities will heavily depend on the outcome of the merger planning work
Hopefully in the next month or two, we will have more clarity around a potential merger
Until there is more clarity, we will proceed similar to 9.0 release
Feature PR Creation Deadline: Friday, February 21, 2025