Page History
...
- (30 mins) General Discussion Topics
- DSpace 7.6 ongoing development
- PR Merge deadline is (rescheduled for) TOMORROW. How is the board looking? What is left to be merged?
- Features needing Documentation in wiki:
- Batch Policy Management - Basic usage documentation
- Signposting (how to enable/disable, basic configs. Could link to the REST Contract for more details: https://github.com/DSpace/RestContract/blob/main/signposting.md)
- Browse Hierarchical Vocab?
- Primary Bitstream?
- Newer High priority bugs located on main branch (Volunteers still welcome, if you find time. Otherwise, these will be pushed back to 7.6.1 bug fix release):
- Submission form "Type" dropdown changes values when pressing Enter: https://github.com/DSpace/dspace-angular/issues/2145 Might be related to Safari browser dropdown issues: https://github.com/DSpace/dspace-angular/issues/2124
- Community/Collection admin permissions problems:
- Cannot add logos:https://github.com/DSpace/dspace-angular/issues/2240
- Configurable Entities bug: When creating a new relationship, the relationship is duplicated: https://github.com/DSpace/dspace-angular/issues/2270
- Releases after 7.6: Later releases will be bug-fix only.
- Tim will bring to Steering the suggestion to switch post-7.6 release numbering to 7.6.1, 7.6.2, 7.6.3 (for eventual bug fix release). This clarifies that 7.6 is the final feature release, and that every later release is a minor upgrade.
- Code review process brainstorms: See Incentivizing Code Reviews and PR Testing
- (No Updates) Demo Site migration to Lyrasis (https://demo7.dspace.org/ and https://api7.dspace.org/server/)
- Exact date of switchover date to be announced.
- (Other topics?)
- DSpace 7.6 ongoing development
- (30 mins) Planning for next week
- Review the Backlog Board - Are there any tickets here stuck in the "Triage" column? We'd like to keep this column as small as possible.
- Review the 7.6 Project Board - Assign tickets to developers & assign PRs to reviewers.
- Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
- Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order
...
Overview
Content Tools