Geo group issues requiring attention
Hi @ebrinkman,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
#39854 (moved) Create Rake task to verify all encrypted data can be decrypted with instance's keys ~"Create", ~"Geo", ~"Manage", ~"P3", ~"S3", auto updated, customer, ~"feature", security -
#38005 (moved) Make health checks and circuit breakers detect missing shards ~"Create", ~"Geo", ~"Geo Replication/Sync", ~"devops:create", ~"feature" -
#19739 (moved) Add maintenance mode/admin mode to allow admins to verify things work well post-upgrade ~"Accepting merge requests", ~"Create", ~"Geo", Geo Administration, ~"Geo DR", ~"Geo Replication/Sync", ~"Manage", auto updated, customer, customer+, ~"feature", potential proposal, production request
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: