Developers Meeting on Thurs, December 4, 2025

Time/Location

04 Dec 2025 from 15:00-16: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 20, 2026
- Feature PR Review/Test Deadline: Friday, March 13
- Feature PR Merge Deadline: Friday, March 27
10.0 Release Candidate: Friday, April 3
10.0 Testathon: April 6-17 (two weeks)
10.0 Translation updates: April 6-17 (during Testathon)
Bug Fix Deadlines
- Bug Fix PR Creation Deadline: Friday, May 1
- Bug Fix PR Merge Deadline: Friday, May 15
Documentation & Release Week: May 18-22
10.0 Release Announced: Tuesday, May 26, 2026

There will be no Developers Meeting on Thursday, November 27 because of the USA Thanksgiving holiday. We will resume meetings on Thursday, December 4.

Agenda

Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
1. DSpace & DSpace-CRIS potential merger activities
  1. Announcement: https://groups.google.com/g/dspace-community/c/xFb4vHsHQHA
  2. New "DSpace-CRIS merger" label in GitHub: https://github.com/DSpace/dspace-angular/issues?q=state%3Aopen%20label%3A%22DSpace-CRIS%20merger%22
2. Integrate ng-dynamic-forms into our codebase and upgrade ng-bootstrap: https://github.com/DSpace/dspace-angular/pull/4898
3. Other topics
  1. Pulling some spring XML from src/main/resources into config folder (e.g. spring-dspace-addon-validation-services.xml) (Kim)
  2. (Please add your own topics)
Board Review:
- 10.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.
- Maintenance Board (9.x, 8.x, 7.6.x) - 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)
- Potentially auto-closing "stale" issues and PRs: https://github.com/DSpace/DSpace/pull/11550
- Revisiting Nx / modularization discussion: Prototyping Nx vs Angular CLI Workspaces
  - Preparation PR (preparing for possible Nx or Angular Workspaces migration): https://github.com/DSpace/dspace-angular/pull/4629
  - Prototype Angular Workspaces PR: https://github.com/DSpace/dspace-angular/pull/4783
  - Original Nx PR (example full migration to Nx): https://github.com/DSpace/dspace-angular/pull/4019
- Follow-up on "aggressive bot" discussion: https://github.com/DSpace/dspace-angular/issues/4565
  - PR to update our built-in "rate limiter": https://github.com/DSpace/dspace-angular/pull/4620

Attendees

Current Work

Project Boards

DSpace 10.0 board: https://github.com/orgs/DSpace/projects/32
DSpace 9.x, 8.x and 7.6.x maintenance 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 10.0

To be decided by DSpace Steering Group with feedback from Leadership Group.

Priorities listed at DSpace Release 10.0 Status.

Goals for 9.2 / 8.3 / 7.6.5

Deadline is TBD for 9.2, 8.3 and7.6.5. 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 9.x. That said, where possible, we'll try to backport bug fixes (especially significant ones) to 8. x and 7.6.x.

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!