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, June 20, 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)
  • (tick) Bug Fix Deadlines
    • NOTE: Because of the number of issues found in Testathon, the 8.0 release is delayed until "high priority" tickets are solved.
    • (tick)  Bug Fix PR Creation Deadline: Friday, May 3 May 31 
    • (tick)  Bug Fix PR Merge Deadline: Friday, May 10 June 14
  • Final Documentation & Release Week: May 13-17 June 17-21
  • 8.0 Release Announced: Monday, May 20, 2024 June 24



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: June 17-24, 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!


Discussed the status and progress of tickets on GitHub (Version 8.0)

Discussed the updated Release Schedule (Version 8.0)

  • Once these have been accepted and merged, development will enter the code freeze phase in order to prepare for release of version 8.0
  • A Release Announcement is planned for early next week (week of June 24, 2024)
  • Documentation (release notes) for version 8 will be reviewed and finalized

Discussed management and maintenance of 7.x and 8.x

  • Tim Donohue created new labels to mark bugs that affect only a specific release or specific branch
  • The maintenance board on GitHub has been renamed to DSpace 8.x and 7.6.x Maintenance

Discussed the release and release schedule for version 7.6.2:

  • There is no strict release date for 7.6.2; the release is planned for shortly after 8.0 has been released
  • 7.6.2 will be released as soon as everything has been tested and the release notes have been finalized 

Version 9.0 (future release) discussion:

  • Tim Donohue will create a brainstorming page to collect ideas for 9.0 on the wiki; everyone is welcome to contribute thoughts and ideas to this page
  • The discussion around ideas for 9.0 revolved around: 
    • Improving performance (high CPU usage,
    • Entities
      • Enabling entities by default in version 9.0
      • How can entities be made more usable?
      • Relationships and nested/hierarchical metadata
    • Shall we automatically change metadata in flyway migrations? 
      • Entities
        • If entities are enabled by default how could a migration look like? Shall we offer a script to add a field dspace.entity.type="Publication" to all items without an entity type? 
      •  DOIs
        • Changing the field a DOI is using (dc.identifier.uri vs. dc.identifier.doi)
        • Changing the resolver ( vs.