Developers Meeting on Thurs, July 18, 2024

Time/Location

18 Jul 2024 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

Agenda

Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
1. DSpace 9.0 release (tentative April 2025)
  1. 9.0 Board is created: https://github.com/orgs/DSpace/projects/31/
  2. Early ideas/brainstorms captured at DSpace Release 9.0 Status
2. Ongoing Discussions:
  1. High CPU with DSpace 7 SSR: https://github.com/DSpace/dspace-angular/issues/3110
  2. Static Site Generation in DSpace: https://github.com/DSpace/dspace-angular/issues/3183
  3. Simplifying the Installation Process: https://github.com/DSpace/dspace-angular/issues/3184
3. (Other topics?)
Board Review & assignments:
- Backlog Board - Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
- 9.0 Project Board - Assign new PRs to volunteers to code review and/or test.
- 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)
- None at this time

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.

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

Page tree

2024-07-18 DSpace Developers Meeting