Page History

...

• (55 mins) General Discussion Topics
  1. 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?
     1. Development priorities for 7.4, given the v5 & 6 EOL announcement. These priorities have been approved by Steering
        1. 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.
           1. We will need to prioritize bug fixes based on severity, likely number of impacted users, whether workarounds exist, etc.
        2. HIGH PRIORITY: Porting of any missing 5.x/6.x features to 7.x from tier listing
           1. Several steering members noted that porting additional Admin Tools would be welcome, especially batch import/export tools.
        3. LOWER PRIORITY: Any other new features (which were not in 5.x/6.x)
     2. During 7.4 planning, we may want to set earlier deadlines for large features.  Existing model works best for small features / bug fixes.
        1. 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
        2. 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.
  2. 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)
     1. 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
     2. 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)
     3. Improve password requirements/management. See for example these tickets https://github.com/DSpace/DSpace/labels/authentication%3A%20password
• (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.

...