 So I will be doing the functional group update. My time says five o'clock. So I'm starting right now and I will start with the screen sharing. Here we go. So welcome to this time's front end functional group update. I'm doing it together today with Philippa and it's a combined group update for the front end AC and DCT. What did we accomplish? We accomplished releasing 9.2. I'm quite sure that everyone is already aware of all the big features that we released with the multiple assignees, the auto refresh especially. Again real-time posting of comments which was already greatly enhanced by Cushar in the meantime so that we get more and more features in there. We have done a lot of optimizations in the search bar so that this feels way easier to use and with the coloring and etc. So what are our concerns over the last weeks and what we saw in this release was basically a problem with the turnover of front end changes. So with the last release especially upcoming to the cut-off date there was a lot of the master was unstable, the tests took very long, a lot of tests were failing simply just to failing etc. So even for small changes that just needed some texture changes or some small UX changes everyone needed to run after their pipelines and run after the tests etc. So what we want to improve in the future and we will come to this point later is simply that you reduce the time and have better and more efficient pipelines on that. Another thing that we will see in the future especially if now with the split of the two teams is that we need unified planning in deliverables and I think there is already a lot of discussions going on between project managers and also in the channels. So this is especially important as the front end ACTC team have focuses from their areas but on the other hand we are sharing a lot of deliverables in between so if we see that someone that the deliverable is not finishable we can pass it over to the other team if that has available resources what already happened in this release cycle. So we need to it's simply about that we have the same format of planning and deliverables all over all the different teams. The other big thing is that we saw especially with the last release was simply that we need to improve the merge request size and delivery. So what happened is simply that it's like a big harbour and on the 7th all the big ships are coming in and so that we make this in smaller chunks and that this is way better digestible over the reviews and also over testing and also over mergers between C and D. So what are our plans for the next release we will be finishing our work on 9.3 tomorrow. The ACTC team will be delivering a lot of nice UX and functional group dashboard improvements. We will have responsive tables over different areas. We are adding two more Prometheus metrics functions. We are improving greatly the Turo settings so you have now the capability of testing your Turo settings way better and this is a way better UX path. So we are doing we have done improvements with UX on the repo settings so they are much better readable and we have inline issue editing from the back end side for the enterprise version we will deliver the server audit logs and there are a lot of more search bar optimizations and features like having the pictures and other tiles and the names of the users in there which feels much nicer if you are doing searches and we do this a lot. For the DC team I'm handing over to Philippa because she can explain the way better than me what the DC team delivered this time. Thank you team. So for the DC team we are going to ship code climates metrics in EE. You'll be able to see it on the merge request widgets. You will also be able to see cross projects in the pipeline graph also on EE and on C you'll be able to see real-time environment stability should be updated real-time. Also some UX improvements and some parts of the job details page will be real-time as well as some parts of the pipeline's show page. We also have a com depth index that allows you to compare to instance of GitLab and it's also possible to search for multiple assignees and start a thread from a not-treaded comment on much requests. Back to you team. Thank you. What are our plans for 9.4 and improving a little bit our pipeline is basically to have a more balanced planning between all the different things that we currently do. So our idea is to have a balance between the deliverables that we are doing with the product managers that we on the other hand also schedule and that everyone is aware of these changes that we are scheduling also every release cycle getting rid of technical depth making efficiency improvements by example this time we want to replace phantom JS with chrome so that simply all our pipelines are running are way more stable and the tests are better in that area. What we also want to do is performance improvements that starts with direct performance improvements by replacing and upgrading bigger libraries perhaps with jQuery and ending with indirect performance improvements so simply that pages feel more faster and that they are not that you have the feeling that something is loading etc so that you are not waiting for a lot. Also this is a big point especially in this release we want to focus a lot on UX improvements and polishing especially based on all the comments that we got from Hekera news we are in very direct contact with the UX team to improve this a lot during this release to get better quality and polishing on all the different areas. We will also take a look if it makes sense to do a time box area fixing what is meant by this is simply that a person can totally focus on a specific functional feature in our product and simply fixes all the issues in that area and on top of that that we also think about the future that we work on POCs where we see okay this can make sense also with the product managers and future advancements and balance out all of these different topics over all our resources and have a better planning so that everyone is also aware of stuff that we are doing behind the scenes. Also that what we want to focus on is that we do in the future more API based similar page applications also looking at GraphQL and that we will do some POCs in that area so that we have perhaps more efficient pipelines because we have very detailed applications and that we are more independent on our tests and have a straighter pipeline for that. Another big thing that is upcoming also for the 9.4 release is feature flags so something that we want to introduce to test out the UX navigation concept which is by the way very very nice in my opinion but do not go for the full thing so that everyone can opt in on these features we will have these feature flags and implement these UX designs as soon as they are ready. Another big topic that we are doing in this release is internationalization so we will do some knowledge sharing so that we spread out the knowledge how to do internationalization so everyone can do it and it's like more of a swarm thing and that we especially do it on new features because then we can go back much faster with internationalization and as we seen in the last weeks the community is very very eager on this topic and is really helping out and wants to translate it in every language so we simply need to make this possible. Yeah that's it first of all I want to thank the frontend team for doing a great release in the last time I'm really looking forward to the next release and it's really awesome to work with everyone as this is especially my first functional upgrade update and yeah that's it thank you for listening and I'm coming to the questions. Tim thanks for the update regarding feature flags that's a functionality that we also want to offer as part of GitLab for the patients you deploy with GitLab are you open to discussing that with Mark Poonsek to see if there's something we can do there? Yeah what we did is as soon as we came up with the idea in the in the menu implementation we came up with the idea to not roll this out fully on GitLab.com but to do this step by step so we reached out to different people and the GitLab team is already working on on some things in there so we will take and reuse what they are doing and we'll closely integrate with them so to have the same feature flags and being able to turn off these things for the detailed things how this is going to work please you need to ask the GitLab team because we're just trying to reuse what they already have what we will need is simply feature flags so based on a user base and also on a group base that someone can turn on and off stuff and we have this on all code paths so that we have it in in Rails that we have it in the templates that we have it in JavaScript that we have it on the API and based on this we can do different stuff we have huge discussions on this in my opinion we should limit this just to really big things that we don't want to roll out heavily on every all the customers I hope this answered your question yep well we'll continue the conversation in the issue thanks any other questions no that was fast great thank you very much and have a nice day and see you in the team call bye take care