GitLab Source Code Group, 16 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.11 Kickoff - Create:Source Code

Description

Source Code group PM (Daniel Gruesso) goes over the work planned for GitLab release 13.11, shipping on 2021-04-22. See planning issue for more info: https://gitlab.com/gitlab-org/create-stage/-/issues/12717.

See the new Git default branch name blog post here: https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/

A

Hi this is daniel caruso. I am the pm for the source code group here at gitlab part of the create stage in the devops lifecycle, and today, I'd like to share with you uh the kickoff for the source codes group, 13.11 version that's going to be shipping on april 22nd of 2021, so we have two big themes for this release.

A

The first one is going to be around supporting the new default branch name for git, um so get recently made their decision and based on communities, feedback about the fact that the default branch name of master is changing. So you know this is based on the community's feedback.

A

Git maintainers, as well as get hosts at large, like gitlab, and so the new branch name is going to be maine and um I'm gonna link a blog post in the description below that has all the details that you need to to know and what we're going to do is we're going to do all the preparation work so on our next major release: gitlab 14.0, uh we'll be shipping with that new default of main and then basically, uh the effort here is twofold: one is going to be around changing that value so that when new instances of gitlab are installed, they use the new default and the second one would be for gitlab.com, so that new projects will use that new default branch name.

A

So it's important to note that this will not affect existing projects or branches. Those will continue to use whatever default name you have, but it will be a change for new projects and new repos. So if it's created on the gitlab gui, then that new default will be used.

A

So that's the first theme that we're going to work on and then any references that we have in the gitlab product. For example, there are some in-app messages that make a reference to the default branch of master, so it's updating all of our all of those hard-coded instances in both the back-end and the front-end to use the new default branch name of main.

A

So when that you see, let's say a message uh after you do an operation uh we'll no longer make a reference to the old default of master, but will it'll be the new default of maine.

A

So that's the first theme and then the second theme is continuing to work on the performance, uh security and resiliency of gitlab.com our sas offering. So that's what we have planned for april. uh You know, as always, feedback is welcome. Please feel free to reach out I'll, see you on the next one. Bye.