Discussion Topics - If you have a topic you'd like to have added to the agenda, please just add it.
8.0 release topics
Feature Review Deadline is Tomorrow (Friday, February 9)! Please get your initial reviews complete for all feature PRs!
Any high priority questions or required feedback regarding new features?
FINAL DECISION : Should we attempt to move the "Content Reports" feature forward as a disabled-by-default, beta feature in 8.0? Or do we delay till 9.0?
A configurable setting must be added so that the Reports feature can be enabled/disabled.
Warnings must be added for DSpace users that want to enable the reports.
All unit test errors from both PRs must be resolved. (Please note that, especially for the Angular layer, it may result in temporarily disabling a few failing tests.)
The merge conflict of the backend PR must be resolved.
Some feedback may not be addressable. Any non-addressable feedback will be turned into issue tickets.
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
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?
A configurable setting must be added so that the Reports feature can be enabled/disabled.
(NEW)Ideally this would also include disabling the backend REST endpoints if this feature is disabled. This could be optional, but may not be difficult to add.
That code will disable the Researcher Profile endpoints whenever the configuration "researcher-profile.entity-type" is unspecified or false. See also other examples in the codebase of where @ConditionalOnProperty is used.
Warnings must be added for DSpace users that want to enable the reports.
All unit test errors from both PRs must be resolved. (Please note that, especially for the Angular layer, it may result in temporarily disabling a few failing tests.)
The merge conflict of the backend PR must be resolved.
Some feedback may not be addressable. Any non-addressable feedback will be turned into issue tickets.
These changes should not be added into DSpace as they bypass the usage of embedded content via Projections. The normal way of obtaining the owning Collection via the Item endpoint would be to do something like this: /server/api/core/items/<:uuid>?embed=owningCollection That request would return the Item information with owning Collection information embedded.
Five +1 votes in favor of adding this to 8.0 as beta feature
One -1 vote opposed. Prefer adding to 9.0
One 0 vote.
Vote passes. This feature can be included in 8.0 as a "beta" feature provided the steps noted above are all resolved/addressed (except where noted that something will not be addressed)