As noted last week, Tim Donohue recommends these to be "1 Approval" pull requests.
While they are large, they've received a lot of feedback over the last year. We have several other features (OpenAIRE Metadata Suggestions & COAR Notify support) which depend on this initial framework.
8.0 release topics
Any 8.0 PRs developers need feedback on prior to the holidays?
(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.
8.0 Project Board- Assign new PRs to volunteers to code review and/or test.
7.6.x Project Board - Assign new PRs to volunteers to code review and/or test.
Upcoming Topics:(Let us know if there are topics you want to discuss in future weeks)
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 8.0
This were decided by Steering in their meeting on June 28, 2023.
Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code)
Include new features which empower users in the admin UI. Make things easier for Admins.
Accepting community contributions of any 6.x features which missed 7.x
Improve documentation, training to allow for greater community contributions. (Ease setup/install/customization, etc.)
Per DSpace 7 WG meeting on June 29, 2023, this may include dependency upgrades/maintenance (Angular, Spring, Solr, Tomcat, etc). May also include necessary code updates/refactors to ease in ongoing maintenance.
Release Goal: April 22 2024
In parallel to 8.0, proof of concepts / planning regarding modularization:
Bug/security fixes only. Release will occur when sufficient fixes have been made to warrant a release.
New "themeable components" (for dspace-angular) are allowed in bug fix releases, provided that they don't significantly modify component behavior or similar.
Bug fixes should have one Pull Request (exceptions may be made for very small fixes)
A PR against either the "dspace-7_x" maintenance branch OR the "main" branch.
(In the case of complex bug fixes, it is possible this automatic port action will fail. In that situation a manual port PR may need to be created.)
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?