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, Nov 14, 2024

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 (DRAFT)

  • New Feature Development Deadlines
    • Feature PR Creation Deadline: Friday, Jan 24, 2025
    • Feature PR Review/Test Deadline: Friday, Feb 14
    • Feature PR Merge Deadline: Friday, Feb 28
  • 9.0 Release Candidate:  Friday, March 7
  • 9.0 Testathon: March 10-21 (two weeks)
  • 9.0 Translation updates: March 10-21 (during Testathon)
  • Bug Fix Deadlines
    • Bug Fix PR Creation Deadline: Friday, April 4
    • Bug Fix PR Merge Deadline: Friday, April 18
  • Documentation & Release Week: April 21-25 
  • 9.0 Release Announced: Monday, April 28, 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

DSpace at OR2025

  • Ideas for proposals are listed on the wiki page
  • If you would like feedback on a proposal, please feel free to send them to Tim or Holger

DSpace 9.0 release

  • We deed to move through the open PRs on the 9.0 Board as we are getting closer towards the end of the year and nearing deadlines
  • If possible, please try to find extra time to work through open PRs on the board
  • Performance related PRs:
    • A lot of performance tickets are open (labeled "performance / caching" in GitHub)
    • Please volunteer or delegate to your staff to work through these in order to push out bug fixes for the next 7.x, 8.x version and for 9.0
    • Briefly reviewed and discussed solutions for #3110, #3584
    • Please make sure to add any fixes that you have implemented locally and create PRs for everyone's benefit
    • Additional performance related PRs: please create them within the next week so we can incorporate them into the next release

9.0 Board Review

  • Reminder of option to trade PRs
  • Discussed and reviewed #9733; Tim added as reviewer, will take a closer look at suggested configuration
  • #9734: Code looks reasonable, possibly needs integration tests
  • Discussed and reviewed #9747
  • #9732: Need to get tests to verify this is working properly; code needs some cleanup

Action items










  

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