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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/11257 Geo: Gracefully handle replication when there is a primary database node failover ~"Geo", Geo Administration, auto updated, customer, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/11012 [Indie Computing] Open discussion for GitLab appliance for Geo use case ~"Geo", Geo Next Gen, auto updated, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/10779 Geo: redirect /edit and /new routes to primary ~"Geo", UX, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9900 Selective Sync of Projects with restricted metadata ~"Geo", ~"Geo Replication/Sync", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9723 Geo: Database replication in the secondary cluster ~"Geo", ~"Geo Replication/Sync", customer+, database, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9410 Route /admin/geo gives 404 ~"Geo", Geo Administration, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9347 Geo: Handle rename/move/delete of Pages ~"Geo", ~"Geo Replication/Sync", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9341 Geo: Backfill GitLab Pages on secondaries ~"Geo", ~"Geo Replication/Sync", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9337 Geo: Replicate new GitLab Pages deploys on secondaries ~"Geo", ~"Geo DR", ~"Geo Replication/Sync", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/9165 Improve usage pings about Geo ~"Geo", Geo Administration, auto updated, feature, ~"telemetry" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/8168 Gitaly Replicas based on Geo replication Architecture decision, ~"Geo", ~"Geo DR", ~"Geo Replication/Sync", ~"Gitaly", feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7919 Distributed build caching with GitLab Geo ~"Geo", ~"Geo Performance", direction, feature, ~"runner" -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7845 Geo: Decide how we are going to expose Wiki synchronization information ~"Geo", UX, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7703 Better differentiate primary instance from secondaries visually in Admin Area ~"Geo", Geo Administration, UX, feature -
https://gitlab.com/gitlab-org/gitlab-ee/issues/7617 Geo: "Recheck"/"Resync" button on a primary ~"Geo", Geo Administration, feature
Hi @rnienaber,
Here is a list of bugs without severity and priority for the team.
We would like to ask you to work with your team to triage the issues in this list. For each issue please:
- Close the issue if it is no longer relevant or a duplicate.
- Assign a Priority and a Severity Label.
- Assign either a versioned milestone or to the %Backlog milestone.
The definition of these labels are defined at:
- Priority Labels (~P1 / ~P2 / ~P3 / ~P4)
- Severity Labels (~S1 / ~S2 / ~S3 / ~S4)
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.
-
https://gitlab.com/gitlab-org/gitlab-ee/issues/11173 Git push SSH proxy may not handle relative_url_root ~"Geo", Geo Administration, ~"bug", workflowready for development
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: