GitLab 13.12 Release Kickoff, 16 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.12 Kickoff - Enablement:Distribution

Description

Kickoff for the Database Group for the GitLab 13.12 release

Planning Issue: https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/807

A

Hello, everyone, my name, is dylan arino and I'm the senior product manager for distribution and today I'll be talking about our kickoff for our 13.12.

A

Release so, as you can see, um the first few priorities might be similar to previous kickoff videos. We will be number one prioritizing anything that is work in progress from 1311.. The second item here is: we want to kind of have a full handoff to the jihu team, on our package building and for number three here.

A

Any production needs that potentially pop up. We would like to respond to you quickly, so those are kind of going to be our three top priorities um and then moving into uh more work that we, we hope to complete um in 1312 the first one being our open shift beta and ga support.

A

So our 13 release was when we're actually releasing our beta support for openshift and in the form of our operator um from the beta. We would like to capture feedback and be able to respond to it in our 13.12 milestone.

A

So that's kind of why on our priorities here I have the data listed, but this will inevitably lead into work that will support rga of openshift and, as as a part of that operator, this operator will also run on vanilla kubernetes. So both of those items are high priority for us. We would like to support openshift in a production way. The beta is not currently for production, so though we will not actually deliver the full ga in 1312. We want to keep moving towards that as quickly as possible.

A

The next item here is 14.0 removals, so 14.0 removals, though, will not be in place and delivered in the 1312 milestone. We want to set up any work. We can so that in 14.0 the work is efficient in actually removing those for the 14.0 release.

A

Moving on to our item number six here is tech debt. So we want to put a little bit more priority around tech debt for the next potentially few milestones, both delivering customer impact and more efficiencies to our own team, which in turn will deliver more impact to our customers.

A

The first one here is a path forward for our secrets, configuration and then there's a couple sub or related issues, but I think the best summation that I can share here um is this comment: there's a few options for our next steps. Many of them are investigative or poc related.

A

This work is important because it will impact file system security needs of our clients, so we want to set ourselves up with a foundation of work um and a path forward for for ourselves to um you know, handle this in the best way possible.

A

One of the biggest security requirements in particular is plain text passwords, so secrets management configuration is going to be kind of a top priority for our tech debt item there moving on here. Another you know, sub item here is pipeline failures.

A

This in particular relates to our own team pipelines and we want to increase the you know our own developer productivity, and this is a high impact item in tech debt for us. If we are able to tackle some of these pipeline improvements, um it'll allow us to work much more efficiently and effective in future milestones, so completing this work now uh will really um allow us to uh work better in the future, so that kind of rounds out our schedule for 13.12..

A

um Thank you very much, and I hope you have a good rest. Your day.