...
The https://github.com/orgs/edx/projects/17/views/1 board tracks the work needed to coordinate and execute a major technology upgrade or similar software maintenance task across many repositories. It also captures and tracks work in an Open edX repository which is orchestrated or implemented by a team other than its owner, so we can clearly and efficiently hand off responsibility for moving the work along when appropriate. It does not capture all the routine software maintenance that can be done within a single repository and team with little impact on others, or infrastructure updates that are largely internal to a single organization’s deployments.
Statuses
Todo - The need to perform a task has been identified, but implementation has not yet started.
In Progress - A team has been chosen to perform the task, and they have started work on it. A PR in this status may have already passed through one or more rounds of review, but it’s on the PR author to take the next steps.
Author Team Review - The author has completed implementation work on the task, has asked their teammates for review, and is waiting for their feedback. The owning team doesn’t yet need to take any action.
Owner Review - Implementation is complete, the implementing team has asked the owning team for review, and that review is not yet complete. The implementing team is blocked on the owning team.
Approved - The PR has been approved by the owning team, but the chosen service level for the task makes merging the implementing team’s responsibility, and they haven’t yet done so.
Done - The PR has been successfully merged.
...
Review any PRs in “Owner Review” and take one of the following actions.
If changes are requested, move the PR back to “In Progress”.
If the PR is approved and “Owner Does” includes “merge”, merge the PR and perform the remaining owner responsibilities from the service level chosen for that PR.
If the PR is approved and “Owner Does” does not include “merge”, move the PR to the “Approved” column.
Set the “Owner Does” field of new recently added issues in “Todo” to an appropriate value.
Check the board before planning the work for each sprint to determine if any tasks of types 1-2 above should be included. Also check the “Merge Forgotten” tab to see if any PRs that the team is responsible for merging were accidentally left with just an approval instead.
If you have an on-call rotation for handling interruptions, please make it one of this role’s responsibilities to periodically check the team’s tab on this board and take steps to perform outstanding tasks of types 1-2 above. The shorter the latency in moving tasks along, the more efficiently we can complete maintenance work, freeing up developers to work on other priorities.
...