Page History

...

See Trading reviews on Pull Requests for how to get immediate attention to that PR!

Notes

Discussed the release of DSpace 8.0

DSpace 8.0 was released on Monday, June 24, 2024. Tim Donohue thanked all committers for their work and their contributions towards version 8.0.
Reflected on lessons learned from work on version 8.0 and what can be improved to help future releases
- Tim Donohue shared:
  - realizing major upgrades earlier in the development cycle; in the development of version 8, the need to upgrade Springboot and Angular was seen somewhat late in the development cycle, which lead to delays
  - improving and streamlining the code review process, which has also lead to delays; this is partly due to a small pool of reviewers

Discussed the release of 7.6.2

Goal: Dspace version 7.6.2 will be released within the next two weeks
Most fixes for 7.6.2 were identified through work on DSpace version 8
Accessibility issues contain a large part of what needs to be done on 7.6.2
Two PRs were created to backport /api/security/csrf REST endpoint: https://github.com/DSpace/DSpace/pull/9599 and https://github.com/DSpace/dspace-angular/pull/3063; Kim Shepherd volunteered to work on them

Discussed ideas for DSpace version 9

Tim Donohue has created a board for version 9 on GitHub: https://github.com/orgs/DSpace/projects/31/; this board serves as a point to collect ideas and brainstorm features and improvements for version 9
Any larger ideas and brainstorming for version 9 can go on the DSpace Release 9.0 Status page on the wiki
- Anyone is welcome and encouraged to add ideas for version 9 development to this page
- Alternative, anyone is welcome to message Tim Donohue with ideas for version 9 development

Continued the ongoing discussion around High CPU usage with DSpace 7 SSR (see https://github.com/DSpace/dspace-angular/issues/3110)

Anyone is welcome to add ideas on how to improve performance issues in the "Brainstorms" section on https://github.com/DSpace/dspace-angular/issues/3110
Discussed ideas of how do improve performance
- Fixes should revolve around identifying the underlying problem, not just patching a workaround solution
- Pascal Becker shared suggestions on how to improve performance by sending fewer larger requests bundled together instead of many small requests
- Discussed performance issues around API calls (private vs. public)

No meeting will be held on July 4, 2024, due to the public holiday in the US

_{(End of notes)}