GitLab 12.6 Release Kickoff, 15 Nov 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.6 Kick-Off - Configure:System

Description

https://gitlab.com/gitlab-org/configure/general/issues/7

A

Oh, hello, I'm, Victor rod and the product manager of the system, group and I would like to present you our plans for the 12.6 release.

A

Oops yep nigh this, so you can see here. Our plans collected together and I will point. I will go through the most important one that, as we think, are the most valuable ones. Some of the dishes here are moving back and work or supporting birth toward these more important issues.

A

So let me start with the server as debugging. This is one of our ongoing issues. Actually, this is the documents hard developers can set a fantastic search and Cabana for the developers me. We don't think that this is a production of the approach, but it's kind of hard developers to the bug fix the bug, be a development and it's only about documentation.

A

Given the work done at the APM group on providing a bit, let manage elasticsearch tech. We don't want to that. This is a preliminary step and we would like to integrate with them in the longer run. Our second issue is about project templates for JavaScript based server, less project. This is actually our the goal with this is to get adoption from developers, so we can know their needs and why they pains and how they want to use Java less.

A

This is not related to obtain a tidbit offering, but it's rated to AWS lambda, and we would provide here very simple approach to most important and related developers who need some kind of back-end work on a debate agenda.

A

Our next issue actually set of issues all of these, which is related to the fact that currently we are not able to upgrade.

A

We don't have a look into the way of a gradient, a native, and this resulted in situation that we just saw just shipped cloud run one months ago, and we had to roll it back to this later, as cloud run, upgraded take a native from zero, seven zero eight and we could not support penaity zero to eight, but these set of developments we would like to support both generate a native a bridge, and they would like to support again cloud run as much as much as we can for this.

A

One of our important feature is that whenever a bit left ATL meets a last important ket version, it would warn the user that his k native is unsupported and would provide guidance how to upgrade it or how to pin they used it lab KC as to his specific energy version, if they would not like to upgrade once we are done with this, we would like to make it well documented.

A

How can if these can be upgraded, which is the first step to basically provide one kick of the upgrades automatic upgrades which are not part of this issue, but would be followed on later.

A

Given we can support more recent versions of creative of a genetic algorithm south we are going to evade a sugar rush library, which means that we will be able finally to support children again, hopefully, for a longer term time than just a few days.

A

Finally, we have two more issues on our 12.6 done, because it is to be our stretch. Goals, though these are related to our viable K native goal, which means that, having these two issues done, we can provide developers very simple and easy way to get started if they have a kubernetes cluster to get started with K native based herbalist.

A

Basically, after installing k native, we would be able to provide them an automatic subdomain using the github pages infrastructure and in the first iteration we can use the provided episode certificate by them and in later stage we would like to add. Let's include support as well.

A

These are our plans for 5.6 and I would like to highlight few issues that we plan for 5.7 as well, because there's one important issue, we think, is a bug. It's a customer buy related to matter most that books that they would like to fix in the upcoming relay. In five point, seven plans for 5.6, and if you have any feedback, please welcome to welcome three chattering. Thank you very much.