Page History
...
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Notes
Dev Meeting Time
- Due to Daylight Savings Time, our meeting time is now 15:00UTC until March 9, 2025
Discussion Topics
- OR2025 proposals are due Dec. 18
- Please add new ideas for presentations, workshops, etc. or feedback to the wiki page
9.0 Release Schedule
- We are aiming for the 9.0 release to come out in April 2025
- See the current Release Schedule at 2024-11-07 DSpace Developers Meeting
- Any thoughts, feedback or ideas regarding the 9.0 release schedule, feel free to let Tim, Holger or any Steering member know
- Concerns were expressed that the April timeline is too tight for a major release
- 9.0 will be a smaller, transitionary release on purpose, which will allow a full year of development time for 10.0; therefore, it is important that we stick to the April 20205 release date timeline
Priorities for 9.0
- There are still plenty of tickets that need to be claimed which address 9.0 priorities as listed on the DSpace Release 9.0 Status page
- Priorities listed on the wiki page marked with a green checkmark have been completed
- Anything that is currently on the list for 9.0 development that will not be completed by April 2025 will be pushed to 10.0 or 11.0
Ongoing Discussions
- Call for testers: PRs from 4Science Team were updated by Giuseppe, they are ready for testing (#3358)
- Additional topics were added to the agenda which relate to the High CPU ongoing discussion issue
- Some sites are seeing an "infinite load time" when editing an item or browsing DSpace – it seems like the DSpace UI gets "stuck" (#3584)
- Assigned to Art
- New possible performance fix (#3585) – would be great to get this PR in and see if it helps with the infinite loop issue
- Assigned to Giuseppe
- Pierre will test the tickets and see if they fix the problem
- Some sites are seeing an "infinite load time" when editing an item or browsing DSpace – it seems like the DSpace UI gets "stuck" (#3584)
9.0 Project Board
- Purpose of reviewing tickets together is to get people comfortable with the process; if you have time, please continue to work on tickets in the "needs reviewers assigned" column
- Reviewed #9718
- Code looks good
- Would be good to have a manual test and an automated test added
- If anyone is using ORCID and item versioning and wants to make sure this is synchronizing properly, please test this
- Reviewed #3224
- Code looks reasonable
- Need someone to test this, please volunteer if you can test this (easier test: only on Angular UI)
- Reviewed #3225
- Claimed by Tim and Mark to test this
Action items
Overview
Content Tools