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 17, 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 9.2 / 8.3 / 7.6.5

Deadline is TBD for 9.2, 8.3 and7.6.5.  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 9.x.  That said, where possible, we'll try to backport bug fixes (especially significant ones) to 8. x and 7.6.x.

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

  • DSpace & DSpace-CRIS potential merger discussions
  • DSpace 9.1, 8.2 and 7.6.4 maintenance releases came out this week!
    • Thanks again for everyone who contributed to these releases and the security fixes especially.
    • Any questions about the security fixes or these release?  No one had any in this meeting.  If you do have questions, email security at dspace dot org (emails all Committers)
  • DSpace 10.0 
    • No updates on the tentative schedule.  It's just there fore reference until more decisions are made on 10.0 priorities
    • 10.0 general priorities are listed at DSpace Release 10.0 Status .  Additional priorities are likely to be added once decisions are made around potential DSpace-CRIS merger.  However, those general priorities are things that can be worked on immediately.
  • Open Discussion / Tickets people want to discuss
    • MyDSpace is having performance issues when you have a large number of Submission Form configurations: https://github.com/DSpace/DSpace/issues/10750 (brought forward by Paulo Graça )
      • Sounds like a possible bug, especially since it's reproducible in 9.0.  Several of us remember some improvements to MyDSpace related to loading too many submission forms at once, but this sounds different
      • Paulo Graça was asked to get more information about what request is taking too long.  UPDATE: He already did that, see this comment: https://github.com/DSpace/DSpace/issues/10750#issuecomment-3084473198
      • This bug ticket needs more eyes / volunteer to investigate further.
    • Old PR related to refactoring Authority Control code to remove (unused) Context parameter: https://github.com/DSpace/DSpace/pull/9842 (brought forward by Kim Shepherd )
      • Reminder this exists and needs feedback from someone who knows DSpace-CRIS well (4Science preferably).  This is useful cleanup for DSpace, but if it could have side effects for the potential DSpace-CRIS merger then we may want to delay it.
      • 4Science has been reminded and they will take a look
    • Updated comments to the "Restore Angular dynamic decorators" PR: https://github.com/DSpace/dspace-angular/pull/4528#pullrequestreview-3029619734
      • Feedback is overall positive on the direction of the PR.  However, concerns expressed that if we move to Nx (see https://github.com/DSpace/dspace-angular/pull/4019), the current script may not align well with Nx restructuring / modularization.  We may need to investigate a different approach which would align better with Nx.
      • We agreed that we need to review an updated Nx PR from 4Science.  They said it should be ready by end of July.  So, the tentative plan is to review it in our first meeting of Aug (Thurs, Aug 7).  Once we see the Nx PR alongside this one, hopefully we will have some better brainstorms regarding how to integrate them together.
  • 10.0 Project Board - Since no other topics were brought to the meeting, we went to the 10.0 Board and reviewed a few PRs together.

Action items




  

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