 So can you hear me at all I can hear you perfectly James right? Okay, so I'm gonna I'm gonna tell the world that we are broadcasting now And also actually use my phone to check. I can find my That we are live YouTube You can do what's up to you James. Do you want to do the welcome? Yeah, I can do it. I just wanted to check. Yeah, no no go for it Since you're just you're talking first Okay, so let me double-check that get lab is streaming now And yep, it looks like so if I can see myself Okay So my phone shows us streaming. I will I will ping this to our slack to let people know that we're live I'm gonna a Sarah. We're and Daniel. We're already live by the way I'm gonna check my screen share works Yeah, just see a nice that inception You would think so this has been solved by now go ahead Sarah. Oh Quick question. This will be the first time I've been joining a kickoff in a long time And I know we've changed the format a bit. Do I need to share my screen? I'm just gonna be talking about some design system additions the benefits etc. I think it would be nice Okay, I have it ready. I just wasn't sure Yeah, usually we we share visuals Okay, great. And since you're last we're just gonna try to go as fast as we can to make time for you because we're still Have the schedule for half an hour and we usually barely make it. So so I'll talk I'll keep my short too. Absolutely. Well, you're last so you can you can use all the remaining time Yeah, we have about 40 seconds per issue as I see it, right Oh, yes, Bobby also noted your last so it has consequences. Namely, you have to you have to do the outro Sarah So what's the outro? I don't know the outro. Well, you have to say is it the best release ever? You have to you have to make a judgment on that and let the world know I Am not sure Josh will be fine because oh, this is Josh The last one I don't really think if you can shut down the live stream without Josh I Think Josh needs to jump in at the end and talk about the best release ever. I don't feel I don't feel like I'm qualified Well, Josh is here, so I'm sure you can figure it out Ask him. I'll be like Josh is this the best release ever and then he can answer me. I think that's how we should do it I'd be awesome. I Thought we are only doing that anymore though. I actually my camera is not working So I need to apparently try and change browsers or something. I'll be right back I thought we aren't doing like someone commented that like we should just like take Do our own thing or someone come like that was being a little bit contrived. I guess I don't know Yeah, have it be more of a conversation and not a pitch Yeah, I think that's fine. That's the one sentence at the end. It's not that big deal, you know Well, so James you can kick it off whenever your clock hits We're in the time zone for 12 o'clock for us. So whenever you want to start. I'll let you take it away and I'll meet myself Right, we'll do I think we got 15 seconds to top of the hour, right? I think it's top of the hour. Good morning. Good afternoon. Good evening wherever you are. Thank you for joining us on the 11.6 kickoff live stream On YouTube if you've got questions, please leave them in the the live chat and we'll do our best to keep an eye on those and answer those As we go through our items I am actually the first to share because Jeremy Unable to dial in at this time. I'll share my screen so you can take a look at some Visuals of what the managed team is going to be building this release So the first item I'd like to share is about add-on runner minutes for get lab.com on get lab.com. We provide Three minutes for using get lab CI, but some people run out and we want to make it easy for you to buy more minutes When you're using get lab CI on get lab.com. So there's gonna be a great improvement for our CI users Also for get lab.com. We're gonna be adding a new subscription table information to the billing screen It's quite hard currently to work out exactly how much you're utilizing your license And this new table will help you understand just that and make subscription decisions next up For on-premises customers who are self hosting get lab.com start a premium or ultimate edition We're simplifying the way we present the license screen information So a license will now show you in a much more easy to understand summary of the usage when it expires and who specifically the license Licensed to Moving on to some non license related features. We've got a nice improvement to add the ability to Disable admin impersonation. So we have this really handy feature where as an instance administrator when you're debugging Feedback from users or trying to help set things up. You can go to a list of users and then impersonate any of those users and see exactly how get lab is presented to them with this new option of the certain Enterprise environments where admin impersonation creates challenges understanding who's doing exactly what from an auditing perspective It can now be disabled across the whole instance This is coming to get lab community edition and core One improvement I'm really excited about is a new design for the group overview. First, let me show you what it looks like today This is what it looks like a nice flat list But we've made some really big improvements to the way projects look and we're bringing the group list in line with this So that we have the nice left alignment and a similar visual structure between projects and groups Obviously, they're distinct, but it'll just bring a more cohesive interface as you're using get lab and And even more great improvements. We're continuing to improve the profile overview With a range of improvements building on the split layout that was introduced last release We're continuing to refine that For everyone so that your profile pages look just brilliant Continuing on the theme of redesigns in the project list Where we're improving the way it looks So actually, this is this is a really great screenshot. It shows you exactly what it looks like We've got this two-row layout with a tiny little logo and information all crammed over the right and if we scroll down and take a look at What we're aiming for It's going to be a much more open layout where project logos are much more prominent So you can really distinguish Which project is which based on their logos? much clearer project title and great Information like access to the number of stars and forks so you can easily identify The popularity of projects and this is going to be really helpful when you're exploring The project lists in GitLab and also we're bringing the language stats through so you can know exactly which language the project is in Without having to open it and take a look So really trying to improve the discovery of projects and this is going to be great GitLab comm users where there's thousands and thousands of different projects that you can explore but also for larger Self-hosted customers that also have a really big number of projects and finally This is probably the feature. I'm most excited about Probably of all the features is this new tooltip So you can roll over someone's name and actually see in really great detail who they are a Bigger profile picture a description of where they are the time in the location where they are and Their status as well, so this is going to be really helpful and just knowing who you're working with and collaborating on a day-to-day basis So those are the improvements coming from manage Victor do you want to tell us what's coming for plan? I sure do so what I have on the on a list here is promote issue to epic with quick action This is an issue that we're actually wrapping up in eleven point five It didn't quite make the freeze cut off earlier this week So we we plan to finish that up very quickly a scrolling horizontally in the roadmap view So if you look at the roadmap view right now, you can scroll up and down to see different issues But you can't go further back in time or farther for out into the future You can change these date ranges, but again, that's limited So what we want to do is allow you to scroll back in time or use some UI to go back in time or forward in time Creating a good lab merge request in a Jarrah depth panel. So that's something A lot of our Jarrah users have been requesting for and it's supported in some other tools And we want you to be able to have a create a merge request directly in the development panel itself inside the Jarrah interface View board config next to search bar. What that means is that in a issue board right now? the actual board config is hidden behind a modal and so we want to expose that information so when you Navigate to the board you can see it right away. So these are just some design concepts That we are experimenting with right now and that we we plan to ship in the upcoming release Search or filter boards and navigation drop down What that means is very simple in the board switcher in GitLab you can go to different boards But if you have a large number of boards, which we do say for example in GitLab CE gilab e in the gilab group then you can search on them very quickly so you can find the board that you want This one is great epic issue list related issue list And so what this is right now if you go to this related issue list as you see here You can see you know the title you can cross it out You can see the path in the state But this future design which we're planning to work on 11.6 will also include things like The due date the mouse on the weight even who's been assigned to the issue so even confidentiality So you can see a lot more information at a glance Finally, I wanted to talk about import CSV into issues. This is something that a lot of our users have been asking about Say that they're they're working in a different Ticketing systems such as Jira red minus on and so forth and a lot of those systems support exporting to CSV So we want to take that CSV export and then import it back into GitLab So that you can continue using your data your legacy data inside GitLab So rather than trying to Support every single integration and doing it all at once We thought that we would start with the CSV support Which makes it a lot easier so some initial concepts are you know just clicking a button and uploading a CSV and then getting an email So very straightforward from your perspective, but very powerful from a future perspective James back to you Thanks Victor Very excited about those improvements We've got a number of great improvements coming in the create area of GitLab This release the first one is to do with the new merge request review feature That we launched in 11.4 and so one of the the great things about the review feature is that you can leave multiple comments and review them and then send them all as one review But you currently receive many many notifications So if I leave 10 comments, I'll still get 10 notifications even if they were submitted as one review In 11.6 what we're going to do is extend this feature and improve the notifications associated with it So that you'll receive one summary notification that describes all the discussion points that were added in the review So one review will generate one email notification. This should help keep your email inboxes less clogged with GitLab notifications so that you can better discern what's going on the next exciting improvement I'd like to share is around a really big Enhancement we're making to the way approvals work in merge requests So one of the common Challenges we have with approvals is that you can currently describe a list of say five six or ten different users and say I need at least two of this list of users to approve this merge request but as teams and projects grow larger and There's lots of different roles involved in delivering new features. You might need one senior engineer to approve it and one product manager and maybe a QA person It's not as simple as just saying I need three people any people to approve this So what we're doing is we're adding the ability to define multiple approval rules And so I think visually the easiest way to show this is what the project settings is sort of roughly going to look like We're still finalizing the designs Instead of just having a list of people who can approve it and account You'll now be able to create multiple sets of approval rules So we can say that I need one UX designer to approve the merge request I need one person from the security team to do a security review And maybe I need three different engineers to do a review These of course can be set to zero and left it essentially made as optional and so that gives you a structured way of sort of Describing who needs to approve things but this can also be used to enforce Yeah, quite powerful approval requirements And so this improvement is going to be coming to get lab premium and we're also going to be using This as a foundation for some even more great codon as improvements building on the work. We've been doing the last few releases The next really exciting change. I'd like to share is Coming to get lab CE and core which is the ability to suggest a change in a merge request if so when you're leaving a comment on Emerge request if I'll be able to click a button add a little code block and type in what the line should be and then Once I've done that there's going to be some kind of apply button So I'll be able to take this suggestion and apply it in one quick generator commit with the change Rather than having to go into my local editor and copy and paste the change in this is going to really make code reviews so much easier in terms of Addressing feedback So that's a it's a really nice improvement that I think a lot of people benefit from on a daily basis The next feature is a maybe a little less exciting for most people but Occasionally we make mistakes and we push really big files that we didn't mean to push to our repositories and one problem with that is that they kind of get stuck there and so There are a range of tools like the BFG repo cleaner that allow you to rewrite history and expunge that data from your Repository but get lab does a range of really clever things to make sure that you don't lose access to dips So if you push a commit to emerge request and leave a comment on it We create a ref to make sure that's never deleted so that your diff is always Accessible and you can always go back to the common and see what the comp was on But Because of that it means that it's almost impossible to reduce the size of the repository So what we're doing is we're adding the ability to upload the object ID mapping file from BFG And delete all those refs If you need to this is kind of a new killer option But if you've made a mistake and pushed gigabytes of data to a repository that doesn't need to be there This is going to allow you to remove it and that's it for the create team Jason over to you Thanks Right. Let me get My screen shared here. All right for the verify team we have a few great features as well The first one is that we're going to be hiding the variables in the UI by default. You'll be able to click on The reveal values button to be able to see what that value is Unless it's a protected variable in which case you won't it won't be available, of course The UI will be improved a bit, but this is where we're starting with that And this will help with making sure that things remain confidential that are supposed to We're also taking a step towards merge trains. This is a big a big change to the way that things work But we're adding the ability to be able to run a pipeline in the context of a merge request So with the way that we're going to introduce that is by having only an accept rules for merge requests that will Allow you to set behaviors in your pipeline that happen only if it's a merge request or only if it's not a merge request This will also expose some new variables to the to the pipeline as well So that you can see, you know, what the merge request ideas what the merge request Description is and and anything like that. So you this is an important first step And it'll be followed up by doing things like adding More behaviors around this and then eventually getting us to merge trains We're also introducing the ability to do triggers in a natural First-class way rather than using the corral commands or API that people use today This is another multi-part item that we'll be working on over the next few releases So we're introducing this with the ability to trigger a job then we're going to allow you to Wait for a job to succeed or just wait for a job to finish you'll have control over that and then we'll also add the ability finally to be able to set that a Pipeline it should be triggered by another pipeline running. So it's sort of triggered by instead of triggered as we have here So this will be a much better way to manage dependencies between products and those sorts of relationships We're also adding the ability to let pipelines be deleted by project owners. This is something that came up as It comes up fairly frequently as a request for people to be able to manage the data That's in their system or just to hide things that were you know Accidentally done that sort of thing. So it'll be an API call that will let you delete a pipeline ID And then finally for the verify team, we're introducing this ability To see upstream and downstream pipelines in the relationship in relationship to the running pipeline in the pipeline graph So you can see here that upstream there's an upstream dependency that ran for giddily that can be expanded And you can see what was run there and you'll be able to do the same thing on the other end And this will go very very nicely with that ability to trigger pipelines and manage them in that way So that's it for verify and I will turn things over to Josh for package Awesome, thank you very much. We got some exciting things coming here for package as well Let me go ahead and share my screen All right, hopefully that's coming through okay the first item is that we want to introduce MPM packages support within our overall package and our packs report within GitLab So to release to go we went ahead and we supported Maven packages And so now we want to go ahead and also add support for MPM as well so some really setting features there for Got no developers and some JavaScript type packages And sort of expanding our support beyond Java languages as well Also on that topic. We're improving our empty state screen And so previously if you went to the packages screen you agreed with a page that Might have a bit ended on a great of explaining what it did and so we have a new empty state screen That's warm. It's helpful links documentation and describes a little more about what it does So excited to get that in as well to improve some of the user experience And also Maven side. We're working to improve The Support we have today and so right now on Maven We have an API endpoint and essentially Maven repo per project and this can be need to kind of pull Independencies across different projects within GitLab. You're gonna have to add sort of n number of Endpoints within your Maven settings file We're now going to add a read-only instance of a Maven endpoint as a beginning place so you can have essentially one Repository you will to add for all of fraud Maven and then pull each of those in the handshakes down more easily And effectively them before and so that's a nice enhancement there for folks should improve some of the user experience of using this feature For our waving customers and so very setting there about our features for packaging and back to Jason for release Thanks, Josh So let's get this up So two things on the release side one of the big ones that's been looked for for a long time is adding pages Support for subgroups. So this is actually coming in from a community contribution. We're super super excited to be delivering this feature and Yeah, very very exciting one And the next up is we're taking a deep dive into how to do mobile development on GitLab There's a lot of a lot of things you can do using GitLab today, but some of the documentation and other Information around how how to do that in the most effective way isn't up-to-date or isn't easy to find So we're gonna take take a pass make that easy to do If anybody follows me on Twitter, you've probably seen that I've been looking for For developers of Android and mobile apps to collaborate with on this. So if you're interested to reach out to me there J4-L-E-N-N is my username on Twitter and that's it for release. So over to you, Daniel Thank you, Jason. Let me go ahead and share my screen here Okay, so on for the configure team the first thing that we're going to work on is going to be group level Kubernetes clusters This is something that we started on 11.5 didn't quite make it to the finish line So we're gonna pick it up and quickly finish it as part of 11.6 And so basically this is the ability to Configure a cluster at the group level so then the projects that are part of that group can leverage that that cluster and It's going to be very similar to what we have today where we will have a Kubernetes option And when you add the cluster itself is going to look a lot like looks today where you can add from GKE Or add it from another provider manually and basically the big things here is is that when you? Visit the cluster section on your project You're going to be able to see if there is a group cluster for for that particular project And also if there are multiple clusters defined, which one is the one that is active for that particular project So we're excited to bring this feature as part of 11.6 Next we're going to work on configuring auto DevOps deployed applications with secrets that are not in the repo So as you know when you have an application that's being deployed by auto DevOps and you need to pass a secret We don't want to store these in as part of the repo as this is not best practice So what our users are going to be able to do is leveraging the variables that we have today. They can prefix a particular variable name With something that will indicate to get lab that this is going to be passed To the application as a Kubernetes secret So let's say if you have a Rails app and you want to put your rail secret here You're going to be able to pass that to the cluster and be stored as a Secret which is then going to be best practice and it's going to be a Lot better from a security standpoint Then the next thing that we're going to work on is going to be adding API support for the Kubernetes integration So as you know right now the only way to create and manage clusters is via the GUI So basically we're bringing that same functionality to the API so programmatically you can basically bring the clusters up and manage them as you see fit and The last thing that we're going to be working on is going to be deploying cert manager to manage clusters and basically this is for the automatic issuance of SSL Certificates and what we're after here is that everything that is related to the cluster. Let's say The apps that you are deploying as part of auto DevOps or your jupyter hub instance It's going to be able to take advantage of the SSL certificate and serve the content the content via HTTPS So we're very excited to bring this this means that your auto DevOps apps are now going to be able to Support HTTPS and all the other apps that are served by the cluster and that is it for the configure team and Josh over to you for monitor Thanks, Daniel. Also some pretty awesome features in particular like can't wait for the SSL support for those applications On the monitor side. We're putting some groundwork into So just do some discovery on error tracking. This is a feature we want to add to our monitoring feature base And so we'll be looking at how we can best Sort of accomplish that here Potentially integrating a tool or perhaps building our own and so we're doing some analysis there of what that could and it should look like And that would we have a great plan that we have decided upon to go forth and execute in the next release We're also going to be working on taking our metrics dashboard And working to utilize our new Charlie library So last release you spent some time identifying a new child ever that we can use Right now the current dash was written in D3 and it's proven to be a little more work and effort to maintain and make sure We don't have bugs and things like that And so where we're moving to a new library get some additional velocity I hope they can have a little better user experience as well and so we'll be doing a kind of a sprint there to Integrate the new trying library for our metrics dashboard and again, hopefully realize those improved velocity Going forward so excited about that Fabio over to you for secure Thank You Josh. Let's see what's new for the secure team in London six So let's start with the group level Security dashboard improvements. So in level dot five We are shipping the group level security dashboard and we want to trade on top of yet in 11.6 introducing metrics and they see it means that you will not just have the list of the vulnerabilities and The counters but you can also see which is the historical data for this information So mainly it is interesting for director of security or this kind of high-level positions They want to see the trends they want to see how the team is going and which is the then which are the numbers for the different kind of security problems and this is the very first Interaction with it. So you can see there is a graph introduced into the same dashboard So you have all the information in one single look and in the future We want to improve this metric even more. There is a product discovery issue that was done in 11.6 In 11.5. So you can take a look at it if you want to see all the further iterations the second Item we want to work on 11.6 is to disallow merge if a explicit license is found So if you explicitly forbid a license to be part of your project There is almost no way Why a dependency should be allowed if the license is not matching is the license sales forbidden So in the merge request widget The merge button will be blocked in case the project has this option enabled And there is a new license. For example, you introduce a new dependency with gpld2 and the project settings Say that the gpld2 is not allowed for that specific project so there is a message and developers can Understand which is the best solution and fix it. It is very similar to the other Blockers we have on the merge request button We also have a bunch of other things a lot of backstage and database things We are iterating on if you are interested in in you can find the full list in our dashboard as usual You can find the link in the document Now James back to you Thanks Fabio Super excited to tell you about a proof of concept that we're building in 11.6 for object de-duplication in fork networks So the first phase of this is Creating when you create a fork of a public project basically making sure that we're not Copying all the same files all over again We don't need to copy all of them and we can use the git alternates feature To reduce disk usage So we're going to be building a proof of concept in this current release 11.6 That will be behind a feature flag and basically demonstrate the the forking workflow and much reduced disk usage associated with that and there's going to be a lot of things that aren't covered in the proof of concept around deletion of the upstream project and changing permissions and things like that But just to share that we're actively working towards this and we expect to have de-duplicated Forks in the near future Back to you Josh, I think Yep, thank you James. That's again really exciting We had a couple of also great items coming for our distribution team as well we have some kind of dependencies that have Fairly old and in particular a run it for example as well as the registry registry in this case It just hasn't had a release from upstream in almost a year and so what we want to do is take some time and Upgrade these the registry upgrade should be here coming soon Which is very exciting has some nice features in this new release and so looking to take advantage of that here again soon and so we'll be kind of Going from the early releases of running our industry and moving up to more recent releases in the case of the registry We'll probably pick a bit of the commit window to jump up to so we don't take the whole list of commits Which is quite large and we can reduce some risk there So we're looking to upgrade both of those in preparation to really kind of jump to latest once they're available on the case of registry We also are working on some exciting work kind of underneath the the coverage here with with GitLab to upgrade to Rails 5 And with the upgrade to Rails 5 that also unlocks some other interesting features We can take advantage of one of the most important feet or most frequently requested features that we hear on the on you Best side is that people want to really kind of separate configuration of passwords and in particular encrypt many of the passwords With the 5.x line of Rails we can now start to take advantage of that With encrypted credentials and encrypted secrets and so we'd like to do some discovery work here with Rails 5 coming So we can be prepared and understand how we will implement this and that way we can accelerate the kind of market of the actual feature itself and now we have a good plan in place and we have evaluated some of the solutions So that's very exciting there to be able to address that here in the near future with that kind of major upgrade to the Rails 5 system We're also working on some improvements to our dependencies as well So we've done some work in the past to show our dependency list for example You can see this here. We're also working to improve the how we render it to folks But you can see we have a huge list of dependencies and in many of these there's even additional dependencies underneath So you can kind of go keep going further under all of these and so the list is quite large And we want to try to up automate this process at least for reports, but also if we can upgrades as well So we're working to do that here in this release to take some of the burden and remove some manual effort That could be point errors as well And kind of again automate this process So it's an exciting work there for the team going forward. Over to you Sarah for some of the design system updates Thanks a lot. Appreciate it. Looks like I've got one minute to tell you about the awesome work We're doing on the design system, but I'll take it. So let me go ahead and share my screen real quick So the GitLab design system. We're naming it pajamas We're really excited about it and this system houses our usability patterns and guidelines for design and development Why are we talking about this at kickoff? We're committed to improving the user experience of GitLab and we're doing that using this design system They're so important that I wanted to share it with everyone So some of the benefits are speed and autonomy designers engineers and pms can work faster with established patterns and documentation to reference Consistency so established guidelines keep our user experience consistent throughout And time so having these established usability solutions gives our designers more time to devote to exploring new problems and problem spaces So I've listed some of the exciting things that we're working on adding to the design system One of the most exciting I'll skip through some of them You can go ahead and click on those links But the most exciting is component documentation inside of design.gitlab Frontend has been working really hard on this Alongside UX to make sure that it is a single source of truth for designers Engineers and pms and with that that's the end of kickoff. Thank you everyone. Have a great day