2021-06-03 DSpace 7 Working Group Meeting

Date

03 Jun 2021 from 14:00-15:00 UTC

Location: https://lyrasis.zoom.us/my/dspace (Meeting ID: 502 527 3040).  Passcode: dspace

• More connection options available at DSpace Meeting Room

Agenda

• (30 mins) General Discussion Topics
  1. Any final OR2021 prep/questions from anyone?
  2. Setting a release date for 7.0
     1. Assuming only "high priority" tasks (~80hrs of estimated dev work).  "Medium priority" tasks become "nice to have", but many/most will be delayed to 7.1
     2. Tentative Dates for 7.0 Final release:
        1. Monday, Aug 2: Public Release Deadline
           1. Internal Release Goal: Monday, July 26 (i.e. we will release early if possible to do so)
        2. July 15: every 7.0 PR merged
        3. June 24 - July 15 code reviews & PR updates (Art out week of July 12, Ben out week of July 5, Tim out week of July 5, Andrea out June 23-July 2)
        4. June 24: every PR created (high priority mainly). Any created by this date are "guaranteed" in 7.0. Anything after may not be included in 7.0.
  3. Ranking of outstanding 7.x features (by DSpace Governance): DSpace Release 7.0 Status#7.x
• (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.0 Project Board - Assign tickets to developers & assign PRs to reviewers.
    • Priority should be kept in mind here. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.  Reviewers/testers should also concentrate effort on "high" or "medium" priority PRs.

Attendees

• Art Lowel (Atmire) 

• Andrea Bollini (4Science)

• Tim Donohue

• Lieven Droogmans

• Giuseppe Digilio (4Science)
• Ben Bosman
• Paulo Graça
• Mark H. Wood 

7.0 Release Goals

These resources define the prioritization and general schedule we are working towards

• DSpace 7 Release Goals : overview of goals/timelines & beta release process
• DSpace 7 Project Boards : our planning/scheduled boards which details which features are scheduled for each Beta release.

Current Work

Project Board

DSpace 7.0 Final Project Board: https://github.com/orgs/DSpace/projects/5

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")

Issue Triage process

• Overview of our 7.0 Triage process:
  1. Initial Analysis:  Tim Donohue will do a quick analysis of all issue tickets coming into our Backlog Board (this is where newly reported issues will automatically appear).
  2. Prioritization/Assignment: If the ticket should be considered for 7.0, Tim Donohue will categorize/label it (high/medium/low priority) and immediately assign to a developer to further analysis. Assignment will be based on who worked on that feature in the past.
     1. "high priority" label = A required 7.0 feature is badly broken or not working. These tickets are considered "blocking" and must be resolved prior to 7.0 final.
     2. "medium priority" label = A required 7.0 feature is difficult to use, but mostly works. These tickets should be resolved prior to 7.0 final (but the 7.0 release will not be delayed to fix these issues).
     3. "low priority" label = A required 7.0 feature has usability issues or other smaller inconveniences or a non-required feature is not working as expected.  These tickets are simply "nice to have" in 7.0 final.  We'll attempt to fix them as time allows, but no guarantees are made.
  3. Detailed Analysis: Developers should immediately analyze assigned tickets and respond back within 1-2 days. The developer is expected to respond to Tim Donohue with the following:
     1. Is the bug reproducible?  (If the developer did not understand the bug report they may respond saying they need more information to proceed.)
     2. Does the developer agree with the initial prioritization (high/medium/low), or do they recommend another priority?
     3. Does the bug appear to be on the frontend/UI or backend/REST API?
     4. Does the developer have an idea of how difficult it would be to fix? Either a rough estimate, or feel free to create an immediate PR (if the bug is tiny & you have time to do so).
     5. Are you (or your team) interested in being assigned this work?
  4. Final Analysis: Tim Donohue will look at the feedback from the developer, fix ticket labels & move it to the appropriate work Board.  If it is moved to the 7.0 Project Board, then the ticket may be immediately assigned back to the developer (if they expressed an interest) to begin working on it.
     1. If the ticket needs more info, Tim Donohue will send it back to the reporter and/or attempt to reproduce the bug himself.  Once more info is provided, it may be sent back to the developer for a new "Detailed Analysis".

Security / Performance Tests

Brainstorming options for security testing & performance testing.  How do we want to handle both of these prior to 7.0 final?

1. Security Review/Scanning of pre-7.0:  See DSpace 7 Security Analysis 
2. Performance testing of pre-7.0: See DSpace 7 Performance Analysis

Notes