 It's time Yeah, I think so. Yeah, so thank you for coming Today I'm gonna try to Summarize in 20 minutes One year in QA LibreOffice QA When I thought about this presentation I I thought about a couple of things I could talk about but in this presentation I'm gonna focus on Baxila which is the the backtrackers we use and basically the main tool we use in QA So about me The QA engineer at the document foundation since September 2016 I'm based in Valencia, Spain, and that's my email and my nickname in IRC or telegram so in this talk I'm gonna focus on Three main topics the first one it's a New reports We got in Baxila during this year then second topic Tickets Three a triash during this time. It doesn't mean Those tickets were reported during this year, but it probably are sometimes they were reported before but they were Triash within the this year and then also I'm gonna talk about those tickets close during the the last year so The frame of time I cover it's from Lhasa Fosden Well a bit a couple of days before so it's from February 1st and then up to This week on Thursday I based this Talk on a couple of blog post I did in the past during this year where I Talk and I share some statistics in Baxila and I also did a similar talk in and LibreOffice conference in Rome but in this one I'm also adding some more information I didn't use in this Block post or that all this talk in the past and for in order to to get the The data I use an script that it's here. You can use it or even improve it and Yeah, I just add the script together all the all the data and well This is the general Build this is from from today. I took the screens of today This is Baxila the LibreOffice Baxila right now. We have 56,000 almost 57,000 bucks reported in general So it's difficult to Kind of summarize Baxila one year In a presentation so I'm gonna use a lot of Charge a lot of pipe pipe charge, maybe it's not the best one, but I don't really know how to Sometimes present this kind of information. So I hope you kind of understand it So first I'm gonna talk about the new reported tickets Well, we have to Do two categories in the reported tickets from on the one hand we have the Bax and on the other one we have the enhancements. So in general during this year little more than 7,000 tickets were reported in Baxila and from those Well, almost 1,000 were enhancements and the rest were Were Bax and it was done by 2,800 people and Here you have the top top 10 Users or people reporting Tickets and we have the list of the the first one who has reported 355 and then Jay Yeah This is how many reports we get every week and The bread one those are the box and In here those are the enhancements and as we can see most of the time the enhancements are Every week they are similar. We have the the similar number of reports, but then Talking about Bax. Well, it depends on the week we have like Release a new version, but I match the the releases and it's not the case So so far I couldn't find any way any reason why we we get more we got more reports this week sorry, yeah, and Yeah, in total we get around 135 reports and for for from those Around 117 are back reports in average And this is the same chart but split by by month so We got in average around 600 new reports every month and from those around 80 are enhancements Yeah, then About the current status of those Reports we got during this year. We see that if we look at the General picture here. We see that right now 33% of those are still open, but then if we split the chart between enhancements and Bax we see that 66 of the 56% of the enhancements are still new While 30% of the Bax are Still new so it's important to differentiate between enhancements, which most of the times are nice to have features and Bax which is From my point of view Things that we have to focus more Although enhancements are important as well And here we see The components We get for each report so right there in both cases is the Component we we get more reports for but then Talking about enhancements. We see that the second one. It's about LibreOffice in general While here the the second one is calc and then we also see here that Android we got we we get like 8% while in here we don't get much which is kind of expected because Android is under development now so people just want to have more features there But probably that also means that we should at some point focus more focus more on Android Enhancements because people is people are asking for that Okay, no, that's everything Yeah, it's not there Yeah, maybe Okay, so yeah, then it's only LibreOffice the product Yeah, probably yeah, and then this is about The version of those reports. This is not really accurate because if someone reports a bug saying it's happening in the Sixth branch in the release this week. It doesn't mean this bug is coming from that version Maybe that bug was there from the beginning But yeah, we see that during this year, which is kind of expected most of the bugs were reported against version 5 or the branch the interior branch, but It's also significant that we are still getting some Inherit from open office or even three LibreOffice three bugs then About those Tickets triage during during this year. Oh Okay, so it should be should fit here well Here we see the number of unconfirmed bugs per week So we see that the number of Unconfirms It's kind of a flat But then at some point we have some peaks where the number of unconfirmed bugs are going up And I think at this point we had the LibreOffice conference So no one was triaging bugs. So that's the reason we we have more Unconfirmed bugs there Ideally we should Have this to zero or at least try to because then The less we have the the faster we can triage triage bugs But yeah, right now like last year it was around 476 and right now it's about 410 so we are kind of going that way although it's going to its long process and here where we see When a bug is confirmed it means it's go it goes from unconfirmed to something in something else So it might be need info or new or resolve Duplicate so it's a every status different than Unconfirmed so during this time five five thousand six hundred tickets were confirmed from those Around 800 were enhancements and the rest were bugs and this triaging was done by 240 people See here we see the top ten and Right now. This is the the status of those Triage bugs or triage tickets. We see that if we look at the whole Picture we see that 45 percent are still new but then if we split it then we see that 71 percent of The enhancements are still new while The bugs 40 percent are new it doesn't mean because we are counting like even bugs reported Last week or last month. So it's really difficult to To get a bug fix reported this week and fix within a week a week. So that's the reason we have The number of Bugs in newer status at 40 percent So probably if we could take another range if we if we took another range of a frame of time like Last year probably the number would be less and here in this chart and Measuring that the the timing In order to triage those bugs. So we see that in five percent Fifty-two percent of the tickets. They are triaging one day and then Within a month we have like 80 percent of the of the tickets triage and then well there are always some tickets which Take longer or there is no way to reproduce them. So we like we have like less than one percent which are more than three years in Unconfirmed status, but then yeah, it's important to to know that Within a month we will we cover like 80 80 percent of them 85 percent of the bugs and Then again the version Well kind of spectate that what most of the triage box bugs are in LibreOffice 5 Probably if we do the same next year, you're gonna be LibreOffice 6, but we also have 15 percent of the of the bugs already in in LibreOffice 6 and then an important part of the Triaging it's also a tagging at the bugs and well An important one I wanted to to remark is tagging bugs are regression so we have During this time around 1,000 bugs were tacked as regression by 78 people and This is the the chart over the time We see that the open regressions is kind of flat although it's Slightly going up, but then the number of total regressions in Baxila it's It's growing faster, but the one we have to care about this one So so far it's flat ideally should go down But as long as it's going faster or like this it's it's good and then well another Important task in Triaging back is to bisect them. So we have around this time. We have around 650 bucks Tuck as bisect it was all my 20 people and It's kind of the same we see that the number of bisected bugs The open ones are kind of flat and then the number of bisected in general it's growing faster and Yeah, we have another this Keyword it's also important to to when the application is crashing or to when there is a Hand in the application. So it was done on 258 bucks and Sorry, that's a mistake there and it was done by 15 people and Then here we see that the status of this back. So when you when a buck is stuck as regression 36% of them are still new But then if we just if the buck is bisected Around 30% are new and then if we add the half back trace Well, if we have a buck trace then it's even lower So it means that the more we can provide to the to the developers the The well, it's gonna reduce the number of open bucks and Here is the the time comparison. So we see that within a month the tag regression tag is at for 85% of the cases and the same for bisected and have a buck trace and Well, this is the the version of this of each Keyword and now well, I'm going to talk about the close tickets So in general close tickets are those who are moved to resolve verify of close or close and here is the top ten people doing that and well, we have around 536 people who has done that and Well So we see that If we focus on on bugs, we see that 20 22% of them were resolved as fixed 22% were resolved as duplicated and then In sufficient data which means The bag was moved to need info then we didn't have any feedback from the user So in the end we close it as insufficient data and here I don't see Like 20% it's work for me, which means the bug Was reported at some point and then the user try it again without a newer version and then it was fixed So this is the chart for the bugs close Every week and we see some peaks here. That's because that week We move all this need info box to insufficient data. So that's the reason we have those peaks there and this is every month and Well, if we focus on those which are fixed then we see that 1866 we're moved to resolve fix here. We have the top ten and it was done by 152 people and If we focus on those which are duplicated it was done by 125 and here is the top five so we here Profile which is developer and in here we see QA people and The time comparison we see that well No, so So let's focus on resolve fix. We see that in 9% of the cases they are close within a day and then around 40% of the cases they are close within a month and Yeah, within a year. It's around 70% of the cases and on the other hand We have the resolve duplicated which normally are close as duplicated within the first day and then around 60% of the cases or 75 65 are close Within a month Sorry, but yeah, I didn't know like how to process all this information, but maybe it was too much for you