Page History
...
- (30 mins) General Discussion Topics
- (5 mins) NOTICE: Starting next week (Thurs, March 31), our meeting will shift to 14:00UTC (one hour earlier), as everyone will now be in Daylight Saving Time. This will be one hour earlier for USA attendees, but the same local time for those in Europe.
- (5 mins) Any updates to share on SWORDv2 discussions per https://github.com/DSpace/DSpace/issues/8188
- (5-10 mins) Online DSpace 7.3 Webinar/Workshop (hosted by LYRASIS)
- Tentative dates would be in mid-to-late June (after 7.3 and after OR2022)
- Would be 1-2hrs long. Would include an update on 7.3 (what's new), a trimmed down workshop (perhaps mostly oriented on simple customizations).
- Materials would be made freely available to others to run similar training throughout the world (via our many User Groups) later this year.
- (10-15 mins) Any assigned 7.3 work needing early discussion?
- Display Item Access Status in Search Results in DSpace 7: https://github.com/DSpace/dspace-angular/issues/1566 (Université Laval)
- Add topics here
- (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.3 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 of our Triage process:
- 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).
- Prioritization/Assignment: If the ticket should be considered for this release, 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.
- "high priority" label = A feature is badly broken or missing/not working. These tickets must be implemented first, as ideally they should be resolved in the next release. (Keep in mind however that priorities may change as the release date approaches. So, it is possible that a "high priority" ticket may be rescheduled if it is a new feature that cannot fit into release timelines.)
- "medium priority" label = A feature is difficult to use, but mostly works.. These tickets might be resolved prior to the next release (but the release will not be delayed to fix these issues).
- "low priority" label = A 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 the next release. We'll attempt to fix them as time allows, but no guarantees are made.
- 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:
- Is the bug reproducible? (If the developer did not understand the bug report they may respond saying they need more information to proceed.)
- Does the developer agree with the initial prioritization (high/medium/low), or do they recommend another priority?
- Does the bug appear to be on the frontend/UI or backend/REST API?
- 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).
- Are you (or your team) interested in being assigned this work?
- 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 Project Board, then the ticket may be immediately assigned back to the developer (if they expressed an interest) to begin working on it.
- 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".
On Hold Topics
- Discussing Release Support now that 7.x is out
- The DSpace Software Support Policy notes that we support the "most recent three (3) major releases" (where a major release is defined by the changing of the first number, e.g. 6.x → 7.x). This would mean that 5.x, 6.x and 7.x are all supported at this time.
- Should we propose to Committers / Governance a change of policy to the "most recent two (2) major releases
- "
- .
Notes
Overview
Content Tools