Developers Meeting on Thurs, May 1, 2025

Time/Location

01 May 2025 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace?pwd=RTk4QUhISnhPRi9YenVrTFJKbDllQT09 (Meeting ID: 502 527 3040). Passcode: dspace

More connection options available at DSpace Meeting Room

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

Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
1. TOMORROW (May 2) is our deadline for Bug Fix Pull Requests to be created for consideration in 9.0. Any Bug fix PRs created after May 2 will not be considered for 9.0 unless they are deemed high priority for this release.
2. DSpace & DSpace-CRIS potential merger discussions
  1. DSpace and DSpace-CRIS Planning Groups - wiki pages to follow along with ongoing discussions.
  2. DSpace-CRIS and DSpace Differences - List of known feature/architectural differences between DSpace 8 and latest version of DSpace-CRIS
3. DSpace 9.0 release (see release schedule above)
  1. Feature Documentation in 9.0 Documentation Wiki Space: https://wiki.lyrasis.org/display/DSDOC9x/Release+Notes
    1. Missing Documentation for:
      1. ORCID Login Flow for private emails: https://github.com/DSpace/DSpace/pull/9849 (4Science)
  2. High Priority bugs / PRs on our board:
    1. `https://github.com/orgs/DSpace/projects/31/views/1?filterQuery=label%3A%22high+priority%22
4. Other topics
  1. (Please add any here that you'd like to discuss)
Board Review:
- 9.0 Project Board - Review PRs collaboratively or Assign new PRs to volunteers to code review and/or test.
- Backlog Board - Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
- 8.x and 7.6.x Maintenance Board - Known bugs can be found here, along with any backported bug fixes.
Upcoming Topics: (Let us know if there are topics you want to discuss in future weeks)
- Ongoing Discussions (temporarily put on hold until there are updates):
  1. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110 (This should be alleviated through several SSR related performance improvements coming in 7.6.3 and 8.1)
  2. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
- Discussion: how to keep message catalogues in sync? https://github.com/DSpace/dspace-angular/issues/3334

Attendees

Current Work

Project Boards

DSpace 9.0 board: https://github.com/orgs/DSpace/projects/31
DSpace 8.x and 7.6.x board: https://github.com/orgs/DSpace/projects/29

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!