GitLab 12.4 Release Kickoff, 10 Sep 2019

Previous Meeting

⏯

youtube image

►

From YouTube: 12 4 Release Kickoff

Description

Kickoff Video for Release 12.4 - Release stage

A

Hi, my name is reka Lewinsky and I'm the product manager for the release stage at hip pub today, I want to walk through what we're planning to deliver in the 12.4 release.

A

So the first thing that we'll discuss is adding the public API for feature fives. We recently delivered the capability to add feature flyers and some associated strategies that could only be done through the UI and now we're adding an extended capability to do this through API, which will also enable using different scripts in order to use this functionality.

A

Next, we're going to add support for allowing fourth pipelines to run in a parent project. We understand that there are many development teams are using this development strategy and our current merge pipelines do not support this capability. So this is a really exciting, we're going to add the ability to use our emerge bike lines for forked pipelines, so this will actually improve the life of quite a few development teams, and we're really excited about this feature.

A

The next three items are kind of grouped together and address the need to manage environments. Today we have many many in environments, maybe even thousands of environments that we need to deal with, and many of them are no longer used and there is no easy way to clean up these environments.

A

So we're going to provide in 1204 release several options in order to clean up these environments, one of them is via API, which also will unlock scripting capabilities in order to delete environments easily and the other two items are related to UI and I will show off the UI a little bit.

A

Please note that this is mock-up and it may change, but basically this is the idea on the environments page itself we're going to have a new buttoning that allows you to clean up environments, and once you hit that butt button, you will see these two options again.

A

The text might change, but the idea is that one of the options will delete any environment that is currently not being used and the other option is the option to to add and fire date for your environments, so once that they is reached, it automatically will clean up the environments.

A

Alright next, my next feature, which is also really exciting, is something that connects kind of feature flags with planning and the release page. So, basically, at the moment, when you create a feature flag, as you can manage it through the feature flag page, but you don't necessarily know the Association to the merge requests or for the issues. So this feature will add this capability.

A

It's a really strong capability and we're very excited about it. So what will it look like so from the future flag? Page itself? You can see now all the related issues to the flag that will be listed here below and, of course, you can add any issues directly from the future flag page. Another addition is from the issue itself, so today, when we have issues you can create related issues or related merge requests.

A

Now we have an additional related feature flags and from the issue itself, you can add the different feature: flags that are related and also from the merge request itself. You will be able to see the related feature Flags listed below.

A

Our next item is the evidence collection for releases. This is a very preliminary stage, but we understand the need for compliance and evidence collection for releases. So in this release, we're going to have the first ever edition to release the release. Page will now have a section called evidence where we're going to start adding slowly different things that you need for evidence such as links to where the build is located for this relation later on, we'll also add binary information, contributors, etc.

A

So we're very excited to be taking our first step into the evidence, collection, realm and stay tuned for it to see where this develops.

A

Our next items are notifications for release and closed status for release pages, and basically, what this means is that we'll have a notification button in the release page and you will be able to select what kind of notification you would like to get when you configure a release, and last but not least, we have making it a possible to creator and it releases using the UI. So up until now, if you made some kind of mistake in the content of the release, you'd have to use an API in order to fix it.

A

Now our ideon adding the capability to allow this to be edited through the UI itself, and that's it for the release stage for 12.4. We're super excited about all the functionality that we're going to be unlocking. If you have any questions or feedback, please feel free to address me directing the issue or email me at corey below in ski, get lab comm. Looking forward to your feedback and super excited for this early No bye.