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


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

  • Testathon is taking place this week and next week
  • Please feel free to take part in it; there is a test plan; please create bug tickets for anything that isn't working
  • Testathon test plan is heavily front-end centered, developers can assist with testing things that are back-end
  • This two week period is also a good time to start the translation process for 9.0, as we are feature complete
    • Question: Is there a list of what is newly created parameters in the English file in DSpace 9?
      • There is a script that marks new keys that need to be updated; Art will create PR for this script: npm run sync-i18n; can be included in release candidate run for next release
  • There a number of test cases that are hard to test (T157, T158, T162, etc.)
    • If anyone has instructions on how to test these, please write them down and share them 

DSpace-CRIS & DSpace Potential Merger

  • There is a new wiki page documenting the differences between DSpace-CRIS and DSpace (both architectural differences and feature differences)
  • Please enhance this page if you know of any other differences that are currently not listed

Testathon Check-in

  • Reminder about Feature Documentation; we have a good number of features in our release notes that are not documented yet
  • Please link to documentation in PR that's created
  • Anything that's not been documented does not get tested in Testathon 
  • Some bugs have already been fixed (e.g. SSR stuff)
  • Look for the testathon label in GitHub to find Testathon-created bugs
  • Bug fix PR creation deadline is May 2; Due date for merging bug fixes is May 16
  • Went through a number of bug tickets
    • #4141: Long bitstreams get cut off at the end of the page; Art volunteered
    • #4140: Already has a fix PR created
    • #4139: Quality assurance notifications not working properly on Sandbox; Giuseppe volunteered
    • #4137: Trying to change file format in bitstream does not work; Giuseppe and team volunteered
    • #4133: Language selection not retained after page refresh (only occurs on Sandbox, not on demo site); marked high-priority; Art volunteered
    • #4132: Not specific to testathon but came up during testathon; having issues with status code on error messages; Assigned to Giuseppe and team
    • #4097: Facets disappear on workflow page; there are two people working on this; Francesco's PR will be closed out
    • #10584: Metadata invisible of withdrawn items
    • #10581: If any of email parameters turn out to be null, the value of null turns up in email; Mark volunteered
  • Art noticed something this morning: on community or collection page, JavaScript is disabled
  • There have been bug fixes applied to the main branch, they have not been pushed out to the Sandbox
    • Tim will push these out tonight or by end of this week, when the least number of people are testing
  • Reminder: Alongside testathon, we still have a lot of PRs that are open on our board
    • If you have time, please review things on the board to be sure we get it into the 9.0 release
    • If you see a PR in the "Needs Reviewers" or "Under Review" column that's of high importance to you, please test it, add a comment, etc. 


Action items











  

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