 Okay, it's time. So I think we can start. Hi, everybody. My name is Jan Pravaznik and I'm a developer in discussion team. I will run the call today instead of Sean McGeverne, who is engineering manager of discussion team, but he is on parental leave today. So let's start with what's new in discussion team. Great news is that we have a new team member, Shantel Rolison, who joined our team this month. And also we will have another new team member, Mark Chou, who will join our team on May 7th. For the second quarter, we are also aiming for one more developer, which will be pretty cool, because currently our team is only of five members, if you are calbing on parental leave. So what are the new features which we added recently or which were improved? The first of them is Elasticsearch. Mario did some improvements and fixes. First of all, we have a new developer documentation, which describes how to set up your local Elasticsearch deployment if you want to run it locally. And also there are some fixes in Elasticsearch token analyzer. Most important of them is fix of kebab case words, which is that so far if you had a word which was joined by a dash, the Elasticsearch analyzer split it into multiple words. So if you were searching for, for example, US dash East, you got matches for US word and also for East word. So currently now it's fixed and you get only desired matches. Another great new feature is subgroup support. Now on issue board list, if you list issues, it's also issues of subgroups are included. So far you were able to include only issues of projects which are part of this specific group. The consequence is that now you can also assign labels from all parent groups to issues in subgroups. And yeah, thanks Philippe for this new feature. Some of the other great new stuff is that we have a performance improvement in match requests. There are some fixes in N plus one queries because on holding match request page, for example, we were always checking whether there is a local branch. Now this is finished. Also we improved usage of our redis cache. Now we cache only highlighted this of the most recent commit if and if a user pushes a new commit, cache highlights for all redis are removed. And we also decreased cache to one week for caching these highlights. Another nice feature is commenting thread for epics. So now you can add comments to epics and as you are used to with, for example, issues. Now you can also attach custom text to each of the email which is being sent by GitLab. And another nice feature is that API now returns information about who closed an issue. What is coming up in 10.8, which will be pretty soon, is we will support email notifications and user auto completion in epics. You will be able to use epics discussions similar to issues and user will get notifications if you mention them in commenting. Also we plan improved notifications settings for groups. If you set notifications settings for one group, this setting will be inherited for all subgroups. There will be also nice new burned down chart for group milestones, which was so far available only for project milestones. And also there will be a new API for commenting match requests and commits. So you will be able to add comments to match request or commits and creative notes through the API. And even further in the upcoming 11.0, we will focus on a couple of big tasks. First of them is team dashboards, which is I think pretty awesome feature. As you are used to use issue boards where you can assign labels by dragging issues across comments, you will be able to do the same, but with assignees. So you can easily assign issues to members in a team. Another nice feature will be batch commenting of match request. So basically you will be able to submit comments for a match request in one batch instead of sending 10 emails separately. And we are also planning to do improvements regarding our Rails 5 support, which I don't think we will finish completely, but at least I hope that we will make a major improvement. So that was the last slide. So now time for any questions. If there are any, let's meet your discussion. Well, there will be an elastic search available for gitlab.com. Honestly, I don't know. I don't think we are planning this for any of upcoming cycles. And we are already replied. Cool. Batch comments on match request. Question is if does that mean we will have a status to indicate the review is done? Actually, good question. I'm not sure regarding this specific status. That would be a separate feature. I think that's been requested in some other context, but batch commenting that feature is just about sending comments and batching them up together so that you're not sending 10 emails. But at least the initial iteration, when you submit the comments, that doesn't change the UI of the merge request comment flow. It will still look like five different comments. So in the future iterations, we would combine those comments. And as you noted, maybe have some status to indicate whether review is done or not. Or maybe integrate that with approvals and so forth. But at least as the feature initially, it's not indicating that status. Thank you. So unless there are any other questions, I think that's all and thank you. See you. Bye.