Gitaly 15.10 Planning (Mar 2023)
This issue and linked pages contain information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes. As with all projects, the items mentioned in this video and linked pages are subject to change or delay. The development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
Table of Contents
Boards
Issue boards we use for planning
Capacity Notes
Objectives and Themes
Please see our direction page section What's Next & Why for our ongoing focus. The list below are specific pieces from these themes.
Disaster Recovery Working Group
The Gitaly team is instrumental in the storage of repository data, and as such, the team has been actively participating in the Disaster Recovery Working Group. As part of this effort, the team is actively engaging with leadership and other teams to investigate backup opportunities and alternative storage methods.
Planning Inputs
Note: The Gitaly team currently does not have a UX component for planning inputs.
Engineering Priorities
Adjust repository maintenance strategy to work with large repositories
- Begin using Cruft Packs in repository maintenance - Start using cruft packs in repository maintenance (gitlab-org/gitaly#4351 - closed)
Continue making progress on allowing Gitaly to push back on traffic surges
- Handle Gitaly limit errors in GitLab Rails (gitlab-org/gitlab#358824 - closed)
- Remove pack-objects limit by user_id and reposi... (gitlab-org/gitaly#4769 - closed)
Quality Priorities
Bug Prioritization Sisense Board - Internal Only. Filter on team_group = gitaly
to see Gitaly specific.
References
Handbook pages which are useful
/cc @eread