Discussion of CMS-activities in DSpace: Several new PRs are adding some basic CMS-light options into DSpace's user interface (namely around Collection/Community homepages). We should review the approaches and ensure that we agree with the direction:
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?
Exclude search & browse components from Angular SSR (#3709)
Seems to work, but there is a visible flash when the page reloads; need to figure out if we can minimize or eliminate that; Tim will re-review (initial review seems lost in GitHub); needs more testing
Moving along, Art has been testing; Tim added as secondary tester
Support configurable limit for exporting items (#10030)
Relatively small; needs reviewers
Processes should only be failed after a Tomcat restart (#10158)
This is a fix to a fix since last release; Tim can review, others welcome to review as well; Andrea volunteered to review
Fix issue where scoped browse throws errors (#3845)
If anyone wants to help test it, please feel free to look at it
On error in DOI organizer bulk operations, continue instead of stopping (#9835)
Optional, relevant to those who use DOIs; two PRs that are somewhat conflicting (#9835 vs. #9869), need reviewing and testing of these; Giuseppe and Vincenzo added
Other topics
Discussion of CMS-activities in DSpace: Several new PRs are adding some basic CMS-light options into DSpace's user interface
Discussed the advantages/disadvantages of allowing custom CSS injection
Highlighted that this would put a different spin on DSpace
DSpace-CRIS already does this to a limited extent
Need to discuss this further, possibly within the context of the DSpace and DSpace-CRIS merger