 Hello everybody, it's the top of the hour so I'm gonna get started. Good morning, afternoon, or night depending on where you are. This is the backend plan update for September 25th, 2018 and I'm presenting it in Rio of Shawn since he's out of office today. So we had some pretty good additions to the team. Right now we are welcoming Brett. He is joining us from the Geo team after their successful migration to Google Cloud and he brings with him a passion for Markdown, specifically Common Mark which he helps ship in 11.1 and 11.3 and in his spare time he develops Versatile Markdown for macOS and he enjoys craft beer and movies. So we're very excited to have Brett on board now on the plant team and now I'm going to show off some interesting additions that we've had these past few milestones. We added milestone dates and epics thanks to Grishal, Pedro and Mark. What this does is it grabs the start and end date directly from the milestones in the issues in an epic. So you no longer have to manually add start date unless you want to. You can just immediately grab the start and end date from the issues that are in the epic. And upcoming, something that's been highly requested is batch comments. We're currently working on it this milestone and thanks a lot to Andre and Pedro for working on this with me. It'll allow you to have a full review, full draft comments and submit them all together as a warm operation. In 11.3 we had some very nice things shipped. We now have a roadmap and epic list view sorting thanks to Grishal and Pedro. We added some extra sorting features here by start date, sort of by the required end date. We now use resource label event for tracking label changes thanks to Jan, Fatih and Grishal. And this will be great help to us in tracking different changes in an issue. So you'll be able to go see the history of label changes in an issue. We also finally enabled common mark for files and weekies thanks to Brett. And this actually allowed us to enable common mark across the board. So we are now officially using common mark everywhere. We now have also usage pings for different board list types. So now that we added a Sine lists and milestone lists, we added usage pings to see how much our users are using these new features. And this is thanks to Shantel. Then we fixed a technical debt issue, which is to use a serializer to render diff lines before we weren't using a serializer. So thanks a lot, Felipe. And we also fixed a blog in JIRA that was duplicating GitLab branches. So if you went into an issue in JIRA and you would see the same GitLab branch just 20 or 30 times. In 11.4, we will be shipping a new filter for the discussions tab in order for you to be able to filter by only comments or on the activity to make it easier to see the discussions or see the changes to an issue. And thanks a lot for to Felipe, Pedro and Constance for working on this. We are fixing system notes generated on epics. We currently do not link to any reference issues. So thanks to Shantel and Annabelle for taking this on. We are adding the ability to close and reopen epics so people can tidy up their epic list a little bit, hide all the epics that you no longer care about, stuff like that. And this is thanks to Jarca, Annabelle and Michelle. And we're also working on seven performance improvements on this milestone. And if we get all of them done, it allows us to reach 100% of our quarter three performance OKR. And a big thing that's also coming is upgrading to Rails 5. We are very close on this. Right now in 11.4, we are solving the remaining issues for running CI on Rails 4 after switching to Rails 5. So with the Rails 5 upgrade comes a lot of changes to the database schema and some of the changes. And so we're making sure that we can still run the CI against Rails 4 in case we need to roll back. So tentatively the plan is to make Rails 5 default in master at the beginning of 11.5 so that during that cycle we can fix any addition on new bugs. And if it's stable, ship will end up 5 with it. And the progress here is thanks to our wonderful community contributors. And as a special shout out, we'd like to thank Blackstone and J.L.A. NICE who have been super involved in this. And these are all the updates that I've had. So let me look in the chat real quick for some questions. So Philippe says it's to upgrade to Rails 5 a shared task with other teams. And that's a yes. We have been taking lead on this, but this is a shared effort between all the back-end teams. Looks like there are no more questions. So thank you everybody for coming to the first FGU I've ever given. I guess I'll give you back the next 25 minutes if you're left. See you in the team call. Thanks a lot.