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.

Developers Meeting on Thurs, May 16, 2024


 from 14:00-15:00 UTC

Location: (Meeting ID: 502 527 3040).  Passcode: dspace

8.0 Release Schedule

  • New Feature Development Deadlines
    • (tick) Feature PR Creation Deadline: Friday, Jan 19, 2024
    • (tick) Feature PR Review/Test Deadline: Friday, Feb 9
    • (tick) Feature PR Merge Deadline (Feature Freeze): Friday, Feb 23 
  • (tick)  Major dependency upgrades: March 3 - March 29 
  • (tick)  Early Documentation & bug fixes: April 1-5
  • (tick)  8.0 Release Candidate:  Week of April 1-5
  • (tick)  8.0 Testathon: April 8-19 (two weeks)
  • Bug Fix Deadlines
    • NOTE: Because of the number of issues found in Testathon, the 8.0 release will be pushed back ~two weeks. 
    • Bug Fix PR Creation Deadline: Friday, May 3 May 17 
    • Bug Fix PR Merge Deadline: Friday, May 10 May 24
  • Final Documentation & Release Week: May 13-17 May 27-31
  • 8.0 Release Announced: Monday, May 20, 2024 June 3



Current Work

Project Boards

To quickly find PRs assigned to you for review, visit  (This is also available in the GitHub header under "Pull Requests → Review Requests")

Goals for 8.0

This were decided by Steering in their meeting on June 28, 2023.

  1. Move forward major features which missed 7.x. 
    1. COAR Notify support (4Science & Harvard): 
      1. Development proposal page: Implementation of the COAR Notify protocol in DSpace 8
    2. OpenAIRE integration with notification broker/claim service (4Science)
    3. Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada)
    4. Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
  2. Include new features which empower users in the admin UI.  Make things easier for Admins.
  3. Accepting community contributions of any 6.x features which missed 7.x
  4. Improve documentation, training to allow for greater community contributions.  (Ease setup/install/customization, etc.)
    1. Per DSpace 7 WG meeting on June 29, 2023, this may include dependency upgrades/maintenance (Angular, Spring, Solr, Tomcat, etc).  May also include necessary code updates/refactors to ease in ongoing maintenance. 
  5. Release Goal: May 20, 2024
  6. In parallel to 8.0, proof of concepts / planning regarding modularization:
    1. Angular : library-based architecture proposal (4Science)
    2. DSpace Preservation-enabled Storage via OCFL (Lyrasis, post-8.0)

Goals for 7.6.2

Deadline is TBD for 7.6.2

  • Bug/security fixes only.  Release will occur when sufficient fixes have been made to warrant a release.
    • New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
  • Bug fixes should have one Pull Request 
    1. A PR against either the "dspace-7_x" maintenance branch OR the "main" branch.
    2. We will automatically generate a PR against the other branch using the "port to [branch]" labels & the "Port merged Pull Request" GitHub Action
    3. (In the case of complex bug fixes, it is possible this automatic port action will fail. In that situation a manual port PR may need to be created.)

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?

See Trading reviews on Pull Requests for how to get immediate attention to that PR!


8.0 Testathon Wrap-Up (and continued testing)

Current priority/focus is on the release of version 8.0, goal is to close as many bug tickets as possible within the next two weeks.

  • Discussed, reviewed, and assigned high priority bug tickets and PRs (angular and backend) on GitHub.

OR2024 Developer Meet-Up & Q&A Workshop

Tim Donohue will attend the workshop virtually. Topics for discussion can be added at OR2024 DSpace Developer Meet-Up and Q&A

Presentation by Michał Dykas on how to optimize SSR performance

Michał Dykas and PCG team shared challenges and solutions on reducing lag times when dealing with large repositories in DSpace.

  • PCG team ran into some scalability/performance issues with a large repository.  Currently documented Performance Tuning DSpace instructions were not helpful enough for a large site
  • Developed a way to use Redis for caching (instead of built-in DSpace caching which uses an in-memory lru-cache).  This Redis solution worked well for a large site
  • PCG will donate Redis integration code & also make suggestions on improving documentation.  (This Redis approach would be optional, only for sites that need it.  However for larger sites it can help alleviate the need for a large cluster of node instances)
  • Slides from PCG presentation