Thursday, Apr 28 (PR Creation Deadline):All new feature (or larger) PRs should be created by this date. (Smaller bug fixes are welcome anytime)
Thursday, May 19 (Review/Test Deadline): All code reviewers or testers should submit their feedback by this date. Code reviews must be constructive in nature, with resolution suggestions. Any code reviews submitted AFTER this date will be considered non-blocking reviews. This means feedback received after Jan 20 is optional to address (unless the team or PR developer decides it is required).
Friday, May 27 (PR Merge Deadline): All new feature PRs should be merged by this date. (Bug fixes can still get in, as long as they are small or important)
Week of May 30: Internal / Early release goal. If possible, we'd like to release 7.3 in late May or first week of June.
Monday, June 6: Public Release Deadline. 7.3 must be announced/released by this date.
Ongoing/Weekly tasks:
Tackle/Claim issues on 7.3 board (starting with "high priority")
(5 mins) Online DSpace 7.3 Q&A Session (hosted by LYRASIS)
General idea is for Tim to record a 7.3 overview/announcement presentation, which is widely distributed to entire comment to watch at their leisure. This talk will likely be pretty much the same as the in-person OR2022 DSpace 7.3 update.
Sometime in the weeks after OR2022, LYRASIS will host an online DSpace 7 Q&A Session with Tim Donohue . This is an opportunity for anyone to ask anything about DSpace 7. (LYRASIS will ask for some questions in advance to help start the discussion.)
Still under discussion with OR2022 as to whether they want to co-host the Q&A Sesson.
(Sidenote: Likely a separate DSpace 7 Online Workshop will be held sometime in the Fall, unrelated to OR2022 or 7.3)
(10 mins) Status check on Code Reviews. We have 2 weeks left in our code review period. Do we feel that's enough time to complete reviews?
Other topics?
(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.
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")
New Feature development process for 7.3
For brand new UI features, at a minimum, the UI ticket should contain a description of how the feature will be implemented
If the UI feature involves entirely new User Interface interactions or components, we recommend mockups or links to examples elsewhere on the web. (If it's useful, you can create a Wiki page and use the Balsamiq wireframes plugin in our wiki)
Feature design should be made publicly known (i.e. in a meeting) to other Developers. Comments/suggestions must be accepted for TWO WEEKS, or until consensus is achieved (whichever comes first). After that, silence is assumed to be consent to move forward with development as designed. (The team may decide to extend this two week deadline on a case by case basis, but only before the two week period has passed. After two weeks, the design will move forward as-is.)
This does mean that if a UI feature is later found to have design/usability flaws, those flaws will need to be noted in a bug ticket (to ensure we don't repeat them in other features) and fixed in follow-up work.
For brand new REST features (i.e. new endpoints or major changes to endpoints), at a minimum we need a REST Contract prior to development.
REST Contract should be made publicly known (i.e. in a meeting) to other Developers. Comments/suggestions must be accepted for TWO WEEKS, or until consensus is achieved (whichever comes first). After that, silence is assumed to be consent to move forward with development. (The team may decide to extend this two week deadline on a case by case basis, but only before the two week period has passed. After two weeks, the design will move forward as-is.)
This does mean that some REST features may need future improvement if the initial design is found to later have RESTful design flaws. Such flaws will need to be noted in a bug ticket (to ensure we don't repeat them in other features) and fixed in follow-up work.
REST API Backwards Compatibility support
During 7.x development, we REQUIRE backwards compatibility in the REST API layer between any sequential 7.x releases. This means that the 7.1 REST API must be backwards compatible with 7.0, and 7.2 must be compatible with 7.1, etc.
However, deprecation of endpoints is allowed, and multi-step 7.x releases may involve breaking changes (but those breaking changes must be deprecated first & documented in Release Notes). This means that it's allowable for the 7.2 release to have changes which are incompatible with the 7.0 release, provided they were first deprecated in 7.1. Similarly, 7.3 might have breaking changes from either 7.1 or 7.0, provided they were deprecated first.
After 7.x development, no breaking changes are allowed in minor releases. They can only appear in major releases (e.g. 7.x→8.0 or 8.x→9.0 may include breaking changes).
Issue Triage process for 7.3
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".