Discussion/proposal around refactoring and simplifying Live Import and External Data frameworks: https://github.com/DSpace/DSpace/issues/9758 (nothing concrete yet but would be great to get thoughts added to this issue and maybe find some collaborators)
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")
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 PRsshould 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?
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
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