Scheduling issue for the 15.[12] release
** This issue is for post-major release issue candidates **
Product Outlook
This is the current outlook for the 15.[123] milestones.
Updated 2022, June 20th for 15.2 milestone
FIPS Audit
FIPS is the Federal Information Processing Standards and are standards and guidelines for federal computer systems that are developed by National Institute of Standards and Technology (NIST). GitLab is pursuing FIPS compliance and the Distribution team has played a crucial role in getting the GitLab application compliant.
We have an audit scheduled after 15.2 so this is the final push to ensure we complete all work related to FIPS so it will be a top priority for Distribution in 15.2.
A few issues Distribution will be working on in 15.2
- Add TLS support config for Workhorse
- Create issues for FIPS compliance checks for Distribution owned components
- TLS security for GitLab Rails metrics endpoints
Distribution long term build efficiency vision
The team is also working to maintain two separate codebases with the same content; Cloud Native GitLab and Omnibus GitLab. This makes our development effort potentially more challenging and lengthy than necessary. The proposal is to consider GitLab and all of its runtime components as one entity and migrating 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 ultimately benefit users by allowing the distribution team to implement more features and be more responsive to community requests by having a more efficient build process.
The first issue is to investigate initial scope. We will continue to tackle issues related in these three milestones.
Improve distribution team pipelines to increase velocity and developer productivity
In the similar theme of our build efficiency, there are improvements to our pipelines that we can make to ensure our team can mitigate unscheduled work due to the complexity of our pipelines. Distribution pipelines, such as those building Omnibus and Cloud Native, grew organically and iteratively as problems were solved. Tight product deadlines and demands have prevented the team from slotting in work to improve the pipelines and take the necessary steps to increase efficiency.
A reduction in unplanned work not only decreases overall workload but, it also allows team members to keep focus on issues and projects without frequent distraction.
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, but before assigning a deliverable milestone. Board includes groupdistribution For Scheduling issues across gitlab-org projects.
Tech Debt board
Prioritized tech debt issues should be scheduled each release to prevent it from growing unchecked. Board includes groupdistribution ~"technical debt" 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.