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, January 9, 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


First DSpace Developer meeting of 2025

Welcome back!  This is our first developer meeting of 2025. 

There is no meeting on December 26, 2024 or January 2, 2025 as Tim Donohue is out of the office from December 20 - January 5.


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.1 / 7.6.3

Deadline is TBD for both 8.1 and 7.6.3.  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

Release Schedule

  • First deadline coming up is Feb 21 for feature PR creation
  • Other deadlines are outline in the release schedule (top of this page) and will follow the Feb 21 deadline
  • Any question regarding the release schedule, please reach out to Tim

OR2025

  • CfP closes on Monday, January 13
  • Proposal ideas are described on DSpace at OR2025, please feel free to add your proposals to this page
  • Please feel free to reach out to Tim or the OR planning committee directly if you have questions

9.0 Planning

7.6.3 and 8.1 Release

  • Want to get performance related fixes reviewed and tested before release
  • Tentative deadline for release is end of January, depending on how the work on performance related PRs progresses
  • Reviewed PRs that need code review / testing:
    • Separate REST APIs for public and private
      • Giuseppe has been working on the backend, got updated today; he is also working on the front end
      • Need help in testing this; feedback from at least 1 individual in a realistic (similar to production) test environment would be very welcome
      • Tim will try it out on his end, but is missing the realistic test environment
      • Goal is to get this tested within the next week
    • Discussed other performance-related PRs:
      • Front-end:
        • #3709: feedback on this is welcome; consider making this configurable
        • #3694: is moving forward, if anyone wants to take a look, please feel free to do so
        • #3682: had a lot of testing and feedback recently; want to add it to the config.example file; if anyone else wants to take a look, please do so
      • Back-end:
        • #10076: no updates on this PR; would be great to get further testing and reviewing on this
        • #10030: reviewers and testers needed; not a large PR; updates the CSV export process; Nick will review
        • #9869: Currently a merge conflict, needs to get updated; anyone who wants to help testing this is welcome

Ongoing Discussions

  • High CPU with DSpace 7 SSR: no updates
  • Simplifying the Installation Process: if you have ideas, reach out to Tim; good to have done sooner than later 

9.0 Board Review Discussion

  • Discussed #9804
  • Discussed #3307: large PR, updating translation files; contains merge conflicts; probably good for 9.0, but hard to backport


Action items

  • Start a discussion around squashing PRs on the mailing list Kim Shepherd