 Hi everyone. Can you hear me? It's 5 p.m. for me. So I think that we should start with the CICD team update. So welcome on to the CICD team update. You can link a link for the previous one from the one that took place one and a half month ago. Maybe let's start with a few things, first thing. Actually, we had Dylan joining the CICD team. Dylan joined us as the senior developer. He's great at helping us on delivering everything that we have planned in our directions. So going straight to the point, let's maybe talk about a few accomplishments. Usually, I put in accomplishments everything that we did before that release. But actually, we did already, we are on the future freeze day for 10.6 and we are 80% or 85% done with 10.6. So I decided to also put the items from 10.6 in the accomplishments. One of the best things that we did definitely like from 10.5 to 10.6 is everything that is related to GKE. There was a lot of different stories that we had to cover. We actually collaboratively worked with other teams that helped us to deliver parts of the stories. But it seems that everything that we planned from the GKE, we managed to finish that. And it's actually something that we're going to promote with the partnership with the Google. So this is accomplishments. You can click on links to actually read through the items that I kind of mentioned in here. For 10.6, this is not the only thing that we kind of mentioned there. There is like crazy amount of other works that is happening in the backstage and across the CI CD product. We actually had crazy amount of different bug fixes that we implemented for artifacts and traces. Something that we work in the scope of the scalability of CI on github.com and GCP migration. We had also crazy amount of different small improvements that not all of them I mentioned but are related to the performance of the CI and reducing the technical depth. Something that we are fighting very hard. Why I mentioned technical depth? Because this is actually one of our lowlights. Actually, this is probably the first time in our releases where we hit something that you could nicely name technical lockdown. So basically, we had that much of the technical depth in some area of the product. In this case, it was the variables processing that even that we had the feature read, we decided to not ship that because it would introduce the bigger problems in the next release because we would have to reward this code completely. So we basically decided that it's not worth to introduce something that is not up to our expectations and not up to the users what they kind of presume how the feature is working and instead focus on getting this resolved and be confident that this is like the app that we should take. If you click on this link prevented us from shipping a major feature, this is actually the variables expression in only an accept syntax. Something that is very useful for all our templates and auto DevOps that makes it makes them like super flexible because user can configure the template without creating their own GitRap CI YAML. Also like the second of the lowlights is like we've been working hard on the GCP migration, but like a lot of small quirks, a lot of small bugs keeps like popping like crazy. And we basically investigate patch, investigate and patch, and we basically do that for pretty much like last month. It seems that we are finally getting a hold of that, but this actually affects our ability to deliver live beats for traces. Something that we planned for 10.6, but due to the fact that we had to take care of the migration code first, we didn't spend time on figuring this out. So these are a few of lowlights, but there is a few more coming from us to 10.7. We actually have a few interesting things because we're gonna, as I mentioned, we're gonna spend one more time to try and fix the variables as that technical lockdown issue. But in this case, not feel the time pressure on hitting the future freeze, but there is like also a lot of other interesting features. For example, if you click the scale deployments, you will see a beautiful screenshots from there where if you go to your environment page, if you configure configure environment, you will be able to say, hey, run this environment in 10 replicas. And if you click a save, this environment will be automatically deployed with the GitLab CI. It makes really powerful solution for autodevils because it will be supported out of the box on autodevils, but this also makes it powerful for users that may want to use the variables that we're gonna expose during that process. This is one of the features, like other one is the project deploy tokens. We want to finally make it easy for creating deployments on Kubernetes that are long-lived. Currently, we only allow to create a token and use that for time of the bit when it's running. But if you want to scale your application afterwards, you don't have like the token that would allow you to fetch registry image, basically, which kind of prevents you from scaling your application across different nodes. As for the GCP migration, we continue live traces, we plan to finally make it happen, and we continue direct upload for artifacts. Because in 10.6, we don't ship direct uploads for LFS. This is 10.7, ciangitlab.com. Actually, it's looking quite great because we are slowly, slowly and iteratively switching our fleet. And currently, the balance is that we work, that we process much more on GCP than on digital ocean. And so far, we don't see any major problems other than these problems with internal DNS. But this is like the issue that we are having from some time, and I know that this is being investigated by our infrastructure team. So hopefully, when we solve this internal DNS problem, it seems that we'll be able to run fully on GCP and all our artifacts and traces will be living on object storage. And this part of the story will be pretty much finished. Hiring, we hire. We are looking for more people. If you have some good candidates, please let us know. We happily interview them. We are looking for people that are passionate about the product, passionate about the CACD space. In particular, may have like DevOps experience. It's also helpful. We work on a lot of different stuff that is related to deployments, to the continuous integration, speed of the continuous integration, something that is very important to our users. But not only that. Also, Kubernetes, it's our area of expertise. So if you know someone, please let us know. We happily try to interview this person. As for the OKRs, it's looking quite decent. We are pretty much progressing on all OKRs. I know that not all APs are yet assigned to people, but we will try hard to finish them in 10.7. And I believe that's it. This is the quick update. Maybe anyone have any questions?