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 6, 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.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

  • Reminders about upcoming 9.0 deadlines.  See 9.0 schedule at the top of agenda.
  • Final steps for 8.1 / 7.6.3.
    • Final reminder to review the release notes for both releases (see links above) if you haven't already 
    • The last "must have" PRs have been approved & will be merged after the meeting: 
    • Final step is to get these PRs backported to 8.x (done) and 7.x (done)
    • Once all of these PRs are merged, Tim will start the release process for 8.1 & 7.6.3
    • Likely that will begin either later today (Feb 6) or early tomorrow (Feb 7).
    • Release Announcement will go out at least a few hours after the release is completed.  This ensures that everything released has propagated to Maven, and DockerHub, etc.
      • Expect to see the announcement on mailing lists on either Friday or Monday. 
  • Question: What is the status of the DSpace & DSpace-CRIS potential merger discussions? Have the groups been created to discuss this?
    • Tim answered:  In the past week these groups were finalized.  There's a Technology group and a Strategy group, and both have a final list of members.
    • Both groups are "invite only" as we need to have a small enough team to discuss these issues.  Both groups have a mix of members who use either DSpace or DSpace-CRIS (or both).
    • Group meeting notes will be public , so that everyone can understand what is being discussed in these groups.
    • Tim & Holger will try to bring general summaries of these discussions (and link in past group meeting notes) to these Developer Meetings.
    • The first meeting of the Technology group is next Thurs (Feb 13) after this Developer Meeting & will be meeting every other week.  Initial meetings will be trying to get everyone on the team up-to-speed on DSpace-CRIS (especially) and the reasons why we might want to merge. So, it may be a few weeks until we have any significant updates to share.
  • 9.0 Board team reviews. Reviewed four PRs today:


Action items