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, April 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


9.0 Release Schedule

  • New Feature Development Deadlines
    • (tick) Feature PR Creation Deadline: Friday, February 21, 2025
    • (tick) Feature PR Review/Test Deadline: Friday, March 14
    • (tick) Feature PR Merge Deadline: Friday, March 28
  • (tick) 9.0 Release Candidate:  Friday, April 4
  • 9.0 Testathon: April 7-18 (two weeks)
  • 9.0 Translation updates: April 7-18 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, May 2
    • Bug Fix PR Merge Deadline: Friday, May 16
  • Documentation & Release Week: May 19-23 
  • 9.0 Release Announced: Monday, May 26, 2025

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 9.0

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

Priorities listed at DSpace Release 9.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

Testathon

  • In today's meeting we will go through bug tickets that have been reported by Testathon
  • Testathon ends tomorrow
  • After tomorrow, we will go into bug fixing mode until the Bug Merger Deadline (May 16)
    • Bug Fixes need to be created by May 2; small bug tickets can be submitted after May 2 (high-priority tickets)
  • We are working on creating tickets for those lines in the test plan that say "Non Compliance"
  • We need to look closer at the lines that say "test unclear"
  • If you have time, please go to the test plan and create tickets for those that say "non compliance", or try to get clarity and see if you can reproduce those lines that say "test unclear"

Discussion Topics

  • Merger: there is a wiki page that lists the differences between DSpace-CRIS and DSpace: DSpace-CRIS and DSpace Differences
    • Feel free to add to this page if you see anything missing
  • Testathon: 
    • Tim has been labeling bug tickets "testathon"
    • If there is anything that's been overlooked, please let Tim know 
  • Feature Documentation: We still need feature documentation for features to be included in 9.0
    • Anything listed on the Release Notes needs documentation 
      • Tim will get in touch with those who haven't done their docs yet to request progress on this 

Discussion of Bugs found during Testathon

Frontend

  • #4213
    • No volunteers at the moment
  • #4211
    • Documentation is wrong, just need to update docs to include the fix
  • #4205
    • Need to see if we can reproduce this; Giuseppe will see if he can reproduce it
  • #4204
    •  Flagged as low priority
    • Impacts all version since DSpace 7
    • No volunteers at the moment
  • #4203
    • Claimed by Kim
    • The Library Code had problems reproducing it; this refers to mobile devices only
  • #4201
    • No volunteers at the moment
    • Is this linked to accessibility? 
  • #4200
    • Pierre volunteered
  • #4195
    • Marked low priority, small usability issue
    • No volunteers at the moment
  • #4194
    • Art volunteered
  • #4187
    • No volunteers at the moment
  • #4172
    • Kim volunteered
  • #4170
    • If you're interested in looking at this, please add a comment in the chat or reach out to Tim after the meeting
  • #4166
    • There has been some discussion on this; there seems to be older code that strips definite and indefinite articles in English, which results in odd behavior in the UI
    • Stefano volunteered
  • #4165
    • Art volunteered
  • #4137and #4132
    • Giuseppe is working on this

Backend

  • #10607
    • No volunteers at the moment
  • #10598
  • #10584
    • Need to investigate what's going on with collection admins and where are the oddities in their behavior
    • Stefano volunteered

Concluding Discussion

  • If there is anything on the 9.0 board that you want to get into 9.0, please test it 
  • You can always offer to do a code review swap, or highlight any tickets in this meeting to get reviewers attention
    • Giuseppe drew attention to and we discussed #3889


Action items











  

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