Page History
...
- (55 mins) General Discussion Topics
- Main topic: 7.4 Release (due Oct 3): Maintenance release only? Or prioritize maintenance first but also allow new features? Which approach do we want to take?
- Development priorities for 7.4, given the v5 & 6 EOL announcement. These priorities have been approved by Steering
- HIGHEST PRIORITY: Stability fixes and major bug fixes. Goal is to immediately fix any major issues we are aware of (or hear about) that might impact production sites.
- We will need to prioritize bug fixes based on severity, likely number of impacted users, whether workarounds exist, etc.
- HIGH PRIORITY: Porting of any missing 5.x/6.x features to 7.x from tier listing
- Several steering members noted that porting additional Admin Tools would be welcome, especially batch import/export tools.
- LOWER PRIORITY: Any other new features (which were not in 5.x/6.x)
- HIGHEST PRIORITY: Stability fixes and major bug fixes. Goal is to immediately fix any major issues we are aware of (or hear about) that might impact production sites.
- During 7.4 planning, we may want to set earlier deadlines for large features. Existing model works best for small features / bug fixes.
- Large features should be broken down into stages / steps. Schedule an earlier PR deadline(s) for those steps. Also schedule review deadlines for those steps
- Goal is to ensure Large features being implementation earlier & get feedback earlier. If they can be broken down into stages/steps, then the final PR & review will be much easier.
- Development priorities for 7.4, given the v5 & 6 EOL announcement. These priorities have been approved by Steering
- Maintenance tasks we feel should be included in 7.4 (Below, please include links to tickets or brief descriptions of issues you feel need to be prioritized highly)
- Curation Tasks are not very usable from the Admin UI: their results are only sent to dspace.log https://github.com/DSpace/dspace-angular/issues/1322 and they cannot restore deleted objects https://github.com/DSpace/DSpace/issues/7956 and cannot run on items https://github.com/DSpace/DSpace/issues/8384
- Resource Policy edit form is confusing & have usability issues. See for example https://github.com/DSpace/dspace-angular/issues/1704 and https://github.com/DSpace/dspace-angular/issues/644 (which is not policy specific but is reproducible when editing a policy)
- Improve password requirements/management. See for example these tickets https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22authentication%3A+password%22
- Provide a way to manage/cleanup Processes, e.g. https://github.com/DSpace/DSpace/issues/7974 and https://github.com/DSpace/dspace-angular/issues/1343 and https://github.com/DSpace/dspace-angular/issues/1660
- Issues with file download from submission/workflow, see https://github.com/DSpace/dspace-angular/issues/1644 and https://github.com/DSpace/DSpace/issues/8378
- General caching issues, e.g. https://github.com/DSpace/dspace-angular/issues/644 and https://github.com/DSpace/dspace-angular/issues/742 and https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22performance+%2F+caching%22
- Statistics display issues, e.g. https://github.com/orgs/DSpace/projects/18?card_filter_query=label%3A%22component%3A+statistics%22
- (Possibly) Restrict system managed metadata fields from editing: https://github.com/DSpace/DSpace/issues/8299
- Feature PRs which missed 7.3
- Recent Submissions Listing on Homepage (Tier 2, donated, smaller PR): https://github.com/DSpace/dspace-angular/pull/1632
- SAF (Simple Archive Format) Import/Export from UI (Tier 3, highly-prioritized by Steering, medium PR): https://github.com/DSpace/DSpace/pull/8318
- OpenAIRE Graph "quality assurance" (notification broker) feature (Tier 4, donated, large PRs but has had several reviews): https://github.com/DSpace/dspace-angular/pull/1562 and https://github.com/DSpace/DSpace/pull/8184
- OpenAIRE "suggestions" (publication claim) feature (Tier 4, donated, large PRs - no reviews yet): https://github.com/DSpace/dspace-angular/pull/1638 and https://github.com/DSpace/DSpace/pull/8280
- Flexible additional metadata for MyDSpace page (Donated, small PR): https://github.com/DSpace/dspace-angular/pull/1621
- Amazon S3 support improvements (arguably not a new feature): https://github.com/DSpace/DSpace/pull/8356
- Port + Refactor event consumer curation code (Queuing Curation Tasks) (donated): https://github.com/DSpace/DSpace/pull/8151/labels/authentication%3A%20password
- Main topic: 7.4 Release (due Oct 3): Maintenance release only? Or prioritize maintenance first but also allow new features? Which approach do we want to take?
- (5 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.4 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