Geo Roadmap FY26 Q3/Q4

Current Q3/Q4 Roadmap

Geo

  1. Improve primary verification experience
    1. Status: In Development
    2. Challenges: FE Engineer is on parental leave, borrowing a resource from Organizations in the next few weeks. We also applied for an UX designer and have not gotten that.
  2. Organization Data Migration
    1. Status: In Progress
    2. Challenges: Resourcing/Capacity, lack of SRE expertise and potentially DBRE expertise
    3. Unknowns: Game Days still need to be planned out etc, a lot of unknowns past rails implementation
  3. Geo on staging
    1. Status: Not Started
    2. Challenges: DRI is currently on PTO, will be a small distraction from Protocells but a big win for Geo to have another environment other than staging-ref due to the amount of data available on this environment and essential to Game Days so we don’t test in production.
  4. Bugs
    1. Status: In Progress
    2. Challenges: Lack of resources, we try to solve this with prioritizing sev 2 data loss bugs but it’s a challenge to get to many of these.  We tried a bug bash a while back to trim this down. 
  5. Maintenance
    1. Status: In Progress
    2. Challenges: Mostly documentation and also refactoring etc efforts by the team/flaky tests when those occur. But had to deprioritize most of the flaky tests 
  6. Dedicated Migrations Support
    1. Status: In Progress
    2. Challenges: One full team member on support in Q3, unknown for Q4

4Q Interlock (commitments you have to other teams)

  1. Geo
    1. FY26Q3
      1. Document/Test with New Container Registry Metadata Database - 18.5 
    2. FY26Q4
      1. Discussions of a possible interlock item for Dedicated Observability Stack for Q1
    3. FY27Q1
      1. None
    4. FY27Q2
      1. None

Next 2 quarters (FY26 Q4 and FY27Q1)

  1. Geo
    1. Product
      1. FY26Q4
        1. Improve primary verification experience
      2. FY27Q1
        1. Level-up available actions to fix problems
    2. Engineering
      1. FY26Q4
        1. Organization Data Migration
      2. FY27Q1
        1. Organization Data Migration

Next 3-5 quarters

  1. Geo
    1. FY27Q2
      1. Level-up available actions to fix problems
      2. Organization Data Migration - Part 2 [PLACEHOLDER] + Cohort 2
    2. FY27Q3
      1. More Organization Data Migration work
        1. Organization migration: Reduce downtime
        2. Organization migration: Improve data integrity
    3. FY27Q4
      1. More Organization Data Migration work
        1. Organization migration: Reduce downtime
        2. Organization migration: Improve data integrity

Needs further scoping/evaluation (in priority order)

  1. GitLab Geo with Logical Replication - was originally on the roadmap but taken off due to resourcing.
  2. Discussion Item: Reduced RPO to 15 minutes by end of FY27Q1: https://gitlab.com/groups/gitlab-com/gl-infra/gitlab-dedicated/-/epics/435 
  3. Tech Debt:
    1. Geo: Git rid of the log cursor
    2. Improving Testing Coverage for Geo
      1. Fix automated Geo installation QA tests 
      2. Add Geo automated end-to-end replication tests 
      3. QA tests on staging-ref with Geo unified URLs
    3. Bugs - I would like to make a bigger dent in our bugs esp if it’s important for Protocells but we need to finish current implementation first and solve the more urgent bugs. 
    4. Geo Troubleshooting Documentation Improvements
      1. gitlab-org/gitlab#562416 - For Dedicated
      2. gitlab-org&11378 - General Geo Documentation
  4. Remote User Acceleration with Container Registry/Other Data Types - also originally on the roadmap but pushed out due to various priority shifts
  5. Revisit the Admin Dashboard along with further dashboard improvements: (Unlikely we’ll get to this item but it was originally planned for) 
    1. Geo: More detailed site status
    2. Stats for data type status counts persistent on UI
    3. Geo: Show count of failed items in replicables view
    4. Geo - Missing Prometheus metrics
Edited by Lucie Zhao