Scheduling issue for the 13.1 release
Product Priorities
-
Support for KMS encryption of objects stored in S3 buckets
This work has been blocked by some upstream changes that needed to happen. The Workhorse changes are being made in gitlab-org/gitlab-workhorse!466 (diffs). The next step is to add support for configuring S3 client credentials for Workhorse in the charts and omnibus. @stanhu might be taking care of the Omnibus changes. I'm not totally sure that we're unblocked on this yet or if we have all the issues we need to support KMS encryption.
-
Test and document Patroni in preparation for officially supporting it as an alternative to repmgr. This unblocks us from adding support for PostgreSQL 12.
-
PostgreSQL 12 in 13.3
- Make a plan that puts us on a good path to add PG12 by 13.3.
- Update the dev docs to include test plans and processes for adding and removing major PostgreSQL versions.
- Address some issues in the PostgreSQL upgrade experience epic
-
Enablement for Helm Chart contributions
Now that we have a little breathing room after getting 13.0 out, this seems like a good time to focus on enablement efforts to help other teams contribute to the Helm charts, with the goal of shifting from creating MRs for other teams to reviewing MRs from other teams.
-
Send Orchestrator into the world (at least the internal GitLab world)
Now that we have the Geo playbook and supporting resources such as a demo video on how to use the Orchestrator, let's focus on internal adoption of the tool so that we can get feedback and iterate.
-
Maturity of the cloud native installation category
Let's spend some time defining what 'Complete' and 'Lovable' actually mean so we better understand what we're working towards. Thoughts on allocating 1-2 hours for a team working session?
Beyond 13.1
Coming up...
-
OpenShift There is a lot of interest in OpenShift and some major revenue opportunities. @ctimberlake1 has been working with RedHat to get the runners working on OpenShift and an Operator to run GitLab on OpenShift. We need to get up to speed on the work that has been done and provide input to ensure this work is supportable.
-
CAC card support in Helm chart. This contributes to the Helm Chart "Complete" maturity epic and we anticipate more requests for this soon as the Helm install adoption by the Federal market picks up. I think we're close to being unblocked on this.
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.
Priority board
Priority board categorizes the importance of all open issues, regardless of milestone. It's useful when looking for issues to consider for scheduling. Board includes issues from Omnibus, Charts, Team tasks projects.
Scheduling board
For Scheduling board is a work board used specifically during the scheduling process to provide an overview of candidates and get an idea of the next release before assigning the milestone to issues. Board includes issues from Omnibus, Charts, Team tasks projects.
Status
-
Collect initial candidate issues -
Issues added to the Deliverable board via label -
Scheduling boards sorted/arranged by importance -
Scheduling boards contain candidates from both Engineering and Product -
Scheduling boards scoped to a reasonable amount of work for the release -
Managers schedule the agreed issues for the release