Scheduling is for the 15.[9,10,11] release
Product Outlook
15.11
Preparations for the Major release
The Distribution team is a key stakeholder in ensuring the major release goes smooth. With that in mind we will be prepping some items in 15.11, since it is the last minor release before 16.0.
Core dependency updates for Cloud Native GitLab
The Distribution team is going to prioritize dependency updates, specifically for Cloud Native GitLab. This includes updating Kubernetes support for 1.22 and 1.25 and updating OpenShift support for 4.11.
Improve Contributor Experience in Distribution Projects
The Distribution team would like to improve how we enable contributors to collaborate on Distribution items. Distribution is a difficult area of GitLab which makes it difficult to know where to start when hoping to contribute to Distribution related item. We want to be able to work with the community more which would help deliver user requested issues more rapidly.
Distribution Long Term Build Efficiency Vision
The Distribution team is working to maintain two separate codebases with the same content; Cloud Native GitLab and Omnibus GitLab.
We should consider GitLab and all of its runtime components as one entity. We migrate our existing build steps into a single process that reduces drift between the products we ship to customers and the resources required to build and maintain those products. This will provide efficiency in every time a build is required for development and ease of customer deployments.
15.10
Core dependency updates for Cloud Native GitLab
The Distribution team is going to prioritize dependency updates, specifically for Cloud Native GitLab. This includes updating Kubernetes support for 1.22 and 1.25 and updating OpenShift support for 4.11.
Improve Contributor Experience in Distribution Projects
The Distribution team would like to improve how we enable contributors to collaborate on Distribution items. Distribution is a difficult area of GitLab which makes it difficult to know where to start when hoping to contribute to Distribution related item. We want to be able to work with the community more which would help deliver user requested issues more rapidly.
Distribution Long Term Build Efficiency Vision
The Distribution team is working to maintain two separate codebases with the same content; Cloud Native GitLab and Omnibus GitLab.
We should consider GitLab and all of its runtime components as one entity. We migrate our existing build steps into a single process that reduces drift between the products we ship to customers and the resources required to build and maintain those products. This will provide efficiency in every time a build is required for development and ease of customer deployments.
15.9
Core dependency updates for Cloud Native GitLab
The Distribution team is going to prioritize dependency updates, specifically for Cloud Native GitLab. This includes updating Kubernetes support for 1.22 and 1.25 and updating OpenShift support for 4.11.
Improve Contributor Experience in Distribution Projects
The Distribution team would like to improve how we enable contributors to collaborate on Distribution items. Distribution is a difficult area of GitLab which makes it difficult to know where to start when hoping to contribute to Distribution related item. We want to be able to work with the community more which would help deliver user requested issues more rapidly.
Distribution Long Term Build Efficiency Vision
The Distribution team is working to maintain two separate codebases with the same content; Cloud Native GitLab and Omnibus GitLab.
We should consider GitLab and all of its runtime components as one entity. We migrate our existing build steps into a single process that reduces drift between the products we ship to customers and the resources required to build and maintain those products. This will provide efficiency in every time a build is required for development and ease of customer deployments.
Issues in Kickoff Video
15.11
- Support Kubernetes 1.25 for Deployment
- Configure CNG build scripts to run multi-architecture Docker build
15.10
- Q1 Efficiency Epic
- Q1 Contributor Epic
- Ensure changes to other components don't break builds
- Have an SSOT page in handbook
- Test GitLab Operator against 4.8 and 4.11
- Support Kubernetes 1.25 for Deployment
15.9
- Support Kubernetes 1.22 for Deployment
- Support Kubernetes 1.25 for Deployment
- Test GitLab Operator against 4.8 and 4.11
- Ensure changes to other components doesn't break package builds
- Add a "What all to test after bumping version of a bundled software" checklist
- Spike: Idea to Parallelize Omnibus Building and Reduce Omnibus Upgrade Diffs
Deliverable Board
Issues on this board have already been reviewed and scheduled for the upcoming release. Each column represents a priority level. The highest ranked issues for each priority level are at the top of each column.
For Scheduling board
Used with continuous scheduling process to provide potential candidates with a preferred milestone, but before assigning as Deliverable. Board includes groupdistribution For Scheduling issues across gitlab-org projects.
Maintenance (formerly Tech Debt) board
Prioritized maintenance issues should be scheduled each release to prevent it from growing unchecked. Board includes groupdistribution typemaintenance issues across gitlab-org projects.
Bugs
Prioritized bugs to be scheduled from input with Quality, Product, Engineering leads. Board includes groupdistribution typebug issues across gitlab-org projects.
Sub-Team Boards
Shows issues broken out by ~"Distribution:Deploy" and ~"Distribution:Build" team labels, to ensure we don't have groupdistribution labels missing their sub-team.
Ongoing Epics
Some epics are used to collect a common series of issues that we are slowly working through release-over-release. This means we typically try to ensure one task from the epic is in each milestone. We are currently marking these with the workflowscheduling label.
Comments
The team is encouraged to add potential candidates and contextual comments to this issue. These are reviewed weekly with PM, EM and Staff engineers to determine impact and priority.