2019-10-07 - Triage report for "group::geo"
Hi, @fzimmer @rnienaber @andr3
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
feature (non-customer)
Unscheduled-
#33252 Resolve (programmatically) foreign table refresh race condition on Geo upgrade Geo Administration, devopsenablement, feature, groupgeo, workflowsolution validation -
#32608 Geo: Warn if cannot find current Geo node Geo Administration, devopsenablement, feature, groupgeo
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 0 | 0 | 0 |
~P3 | 0 | 0 | 19 | 4 | 0 |
~P4 | 0 | 0 | 3 | 12 | 0 |
~"No priority" | 0 | 0 | 0 | 0 | 4 |
Unscheduled ~bug (non-customer)
-
#33385 (closed) Geo: Don't buffer log cursor output when using stdout option ~"Cloud Native", ~"Geo : Kubernetes", Geo Administration, ~"P4", ~"S4", ~"bug", devopsenablement, groupgeo, ~"kubernetes" -
#33376 (closed) Remove "Local" qualification on synced progress bar titles since Object Storage is no longer a limitation Geo Administration, ~"bug", devopsenablement, groupgeo -
#33331 Container repository sync status 100% when nothing synced Geo Administration, UX, ~"bug", devopsenablement, groupgeo -
#32808 (closed) Geo: LogCursor --debug
option does not work ~"bug", devopsenablement, groupgeo, regression, regression:10.x -
#32406 (closed) Geo status API endpoint fails in schema migration Enterprise Edition, ~"P3", ~"S3", api, ~"bug", devopsenablement, groupgeo, ~"validation::problem [DEPRECATED]"
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: