Page History
...
See Trading reviews on Pull Requests for how to get immediate attention to that PR!
Notes
9.0 Release Schedule
- Tomorrow, Friday, May 16 starts code freeze. Anything that doesn't get merged by tomorrow won't get into 9.0 (except for severe, absolutely necessary clean-up work)
- Next week is final testing time, updating documentation, etc.
- Release will come out near end of next week; announcement will occur the following week
Updates and Reminders
- Open Repositories is coming up; if you're able to attend, there is a DSpace Developer Meet-Up and Q+A
- Add any topics to this page if there is anything you'd like to discuss or if you would like to lead a discussion, showcase your repository, feature, customization, etc.
- Feel free to reach out to Tim if you have any questions
- All DSpace-related presentations, talks, workshop at OR25 are listed on DSpace at OR2025
- Merger: No new updates; discussions are ongoing in the Strategy and Technology Group
9.0 Release
- High Priority PRs still being merged before the deadline: https://github.com/orgs/DSpace/projects/31/views/1?filterQuery=label%3A%22high+priority%22
- #3889:
- Moving along, can hopefully be merged after this dev meeting
- Allows users to manage capturing correlation ID in cookie pop up
- Does not need to be backported to 8.x or 7.x as this is specific to the orejime library (previous versions use claro cookie)
- Other PRs are waiting on #3889
- #3613:
- Allows users to manage how long pop-ups stay around
- Configure how long messages occur in live region (e.g. for screen readers)
- Impacts cookie consent pop-up
- Once 3889 is merged, we can get this reviewed and merged before the deadline
- Backported to 8.x and 7.x
- Anyone who wants to do final testing of this functionality, Tim would appreciate additional help
- Other PRs (not high priority): https://github.com/orgs/DSpace/projects/31/views/1
- We will try to get the "Reviewer Approved" PRs still merged
- #3390:
- Plan to merge this right at the end
- This PR helps with code cleanup and restructuring and sets us up for future development (10.0, potential merger, etc.)
- There are new linting rules that will be applied
- Also discussed #4329 in connection with linting rules
- Art will try to review this one right after the dev meeting
- As long as this one works fine, we can get this in before the cut-off date; is currently passing automated tests, needs manual testing
- Also discussed #4329 in connection with linting rules
- #10611:
- Ready to be merged; minor change to ensure that iiif manifests have correct mime type
- #10730:
- Fixing a bug, REST API returning improper status code (currently 200, should be 404)
- Has automated tests; actual fix is only 15 lines of code
- Will test this more on UI side, has a slight chance of having side effects in UI
- Raised the question whether 200 ok is actually the correct error code; an empty list with a 200 ok seems to be a valid result
- This also needs to be consistent with other parameters, such as filters, DSO types
- We will delay the PR and have more discussion around this ticket; suggestion: we could return a 204 code
- #3390:
- If anyone is still doing translations for 9.0, Tim will do his best to get these in by today or tomorrow
- Tim will do a quick scan for performance, accessibility and translations PRs to see if there are any "quick wins" that we can include in 9.0
- Next week's meeting: we will finalize the release, getting things ready for the release
- Looking towards bug fix release for 8 and 7
- What comes next? 10.0 discussion, dependent on merger, but we can start brainstorming things we'd like to recommend back to Steering
Action items
Overview
Content Tools