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, July 10, 2025

Time/Location

 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040).  Passcode: dspace


10.0 Release Schedule (TENTATIVE - Not Finalized)

  • New Feature Development Deadlines
    • Feature PR Creation Deadline: Friday, February 20, 2026
    • Feature PR Review/Test Deadline: Friday, March 13
    • Feature PR Merge Deadline: Friday, March 27
  • 10.0 Release Candidate:  Friday, April 3
  • 10.0 Testathon: April 6-17 (two weeks)
  • 10.0 Translation updates: April 6-17 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 1
    • Bug Fix PR Merge Deadline: Friday, May 15
  • Documentation & Release Week: May 18-22 
  • 10.0 Release Announced: Tuesday, May 26, 2026

Agenda

Attendees

Current Work

Project Boards

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")

Goals for 10.0

To be decided by DSpace Steering Group with feedback from Leadership Group. 

Priorities listed at DSpace Release 10.0 Status. 

Goals for 8.2 / 7.6.4

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 PRs should 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?

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

Notes

10.0 Schedule

  • No updates 

DSpace & DSpace-CRIS merger

  • Technology group met last Thursday and documented dependencies (architectural dependencies, or feature dependencies)
  • Working on a matrix which features have dependencies
  • The Strategy group is working on a communication piece to share an update with the community

Maintenance Releases

  • There has been a delay because a couple of security issues were found
  • Currently fixing these for 8.2, 7.6.4 and 9.1
  • Planning to release these by next week; draft release notes are on wiki
  • We are not adding more bug fixes to these releases at this point in time
  • There will be PRs that serve as patches

DSpace 10.0

  • No major updates; there is still plenty on the board that can be reviewed / tested
  • Direction of 10.0 depends heavily on Merger decision and further input from Planning Groups

Upcoming Topics

  • Angular dynamic decorators – Atmire is still working on it and refactoring the code for easier reading and reviewing 
  • Migration to NX: 4Science is working on a new PR and will bring it to next meeting once it's ready

Other Topics

  • Discussed backend PR #10554 (connected to frontend #4368)
    • Tim and Giuseppe added to see how these work in more detail
    • Atmire will add documentation on how bitstream URLs are working in this PR
  • Discussed issue #11003
    • Once Pierre has feedback on the new ORCID types, he will create a new PR
    • Moved into 10.0 board
    • Question was raised in how far this touches on #10820?
      • Would be nice if these could be linked together or tested together
  • Discussed backend PR #10774
    • Has had some testing and a code review
    • 4Science will review as well
  • Pierre has created tickets for improvement on ORCID model and ROR
    • Discussed frontend #4533
    • Briefly reviewed #4532 (ROR)
      • Provides a richer integration to keep records up-to-date
    • Briefly reviewed #4529 (ROR)
      • Pulled over into 10.0 Board
  • Discussed the idea of creating a code repository for developers so that others are aware of what's available (e.g. for utilities)
  • There is a webinar series currently being prepared: DSpace Deep Dive; if you have any topics that you would like to present on, please contact Tim or Holger

Action items




  

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.