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, February 13, 2025

Time/Location

 from 15:00-16: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
    • Feature PR Creation Deadline: Friday, February 21, 2025
    • Feature PR Review/Test Deadline: Friday, March 14
    • Feature PR Merge Deadline: Friday, March 28
  • 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. 

Early brainstorms at DSpace Release 9.0 Status.  Please feel free to add your own brainstorms or link in tickets that you wish to be considered. 

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

DSpace 8.1 / 7.6.3 releases

  • DSpace 8.1 and 7.6.3 have been released; congratulations and thank you to everyone who contributed; if any contributors are missing from the reference in the Release Notes, please let Tim know

DSpace 8.1 / 7.6.3 releases

  • The two planning groups are now starting their biweekly meetings
  • Wiki pages for both groups have been created
  • Both groups will provide recommendations to Steering as to the merger
  • Updates on the groups activities will be forthcoming
  • Please feel free to ask if you have any questions

DSpace 9.0 release

  • Feature-PR creation date is coming up: February 21, 2025
  • This is a hard deadline; however, small extensions are possible if you let Tim know as soon as possible
    • Question: What about accessibility fixes? Does the PR-creation deadline apply to those? Answer: It depends on the accessibility fix: if it's a large, feature-like PR, it will fall under the Feb 21, 2025; however, most accessibility fixes tend to be smaller in nature and fall under the bug fix category (deadline of May 2)
    • Question: If anyone wanted to do translation work and don't miss any keys, would that be after the translation deadline? Answer: Most new translation keys are added during features; after the merge deadlines have passed and we are preparing for testation, that would be a good time to get any new translation keys in (early April, after March 28 Feature PR Merge Deadline)
      • Discussed how to improve the translation process workflow - Pierre Lasou will investigate and start the discussion with DCAT; Pierre mentioned the tool Weblate

Other topics

  • Adding CSV export to DSpace Admin Reports
    • Pierre and Jeff Morin gave updates; PR is almost ready to go
    • Question: initial recommendation was scripts & processes type export; is it working this way? Answer: Yes
  • Adding more e2e (end-to-end) tests to the DSpace User Interface
    • Steering has discussed this and is eager to make this happen
    • Benefits: will make PR reviews easier; will also lessen the role of the Testathon and help out DCAT; also helps with dependency upgrades
    • This is not a hard lift - if anyone is interested in only doing 1 page, this could be done quickly; junior devs are encouraged to look at this; also an opportunity for Service Providers to give back code per the Registered Service Provider agreements
    • Question: can we split this in different subtasks? So that it can be done by more than one contributor. Answer: GitHub just added a new feature: creating sub-issues; can create subissues now if anyone wants to look at a particular aspect; Tim will start with creating a couple of subissues that he wants to look at; feel free to reach out to Tim or create your own subissue if you want to claim a specific feature on one page
  • Discussion of ticket https://github.com/DSpace/dspace-angular/issues/3070
    • Suggestion from Giuseppe is to remove the link from the thumbnail
    • Not a high priority item - we will continue to discuss this and think about it

Board Review

  • Remove context parameter from AuthorityValueService methods (#9842)
    • Looks reasonable; but need to check if this could conflict with merger with DSpace-CRIS
    • Giuseppe assigned by Tim, he will review
    • Also need to look into whether we need the LogHelper.getHeader method (Line 223) - Mark H. Wood will investigate
    • Moved to "Under Review"
  • Provide new CoverPage implementation (#9844)
    • Looks like it's been moving along
    • Will bring to future discussion if necessary; there are some outstanding questions on the template engine (Thymeleaf)
    • If you have thoughts on this, add them to the comments in the PR

Action items











  

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