This is a quick wrap-up entry for Plasma Bug Days which was held over the last two days. First, we accomplished a lot. I mean a lot. The first goal was to drop into third place on the Weekly Bug Report. We accomplished that on the first day and so moved onto another goal suggested by one of the participants: have fewer reports open than we did six months ago. We also accomplished that. Now we have a new goal: break 1000. We're just 120 reports away from that goal right now.
Today has been relatively slow going as it isn't an official Bug Day so just a few showed up to do bug triage today. Quite promisingly, though, some people from the Bug Days showed up today again. I do hope all of them continue to be involved and help with the bug wrangling as their efforts were just fantastic this weekend.
I also set about to fix some of the older and more annoying issues in some of the more commonly used parts of Plasma Desktop. Many commits later, and many already-fixed (along with some won't or can't fixes, too), and the bug report count has dropped yet further. 4.8 is going to be a fantastic release.
Yesterday was really invigorating, as well: even more people showed up for day 2 than for day 1. That's understandable as it was the weekend. Together we mowed through large quantities of bug reports.
We also pulled together some Plasma bug hunting documentation for newcomers. It was very clear that handing out bugzilla account upgrades to those who took the time to show up was really worthwhile as well: it empowered people who may not have otherwise asked to help out, and boy did they ever.
I used to host bug days sem-regularly, but with project growth and life business they fell to the wayside. I'm happy to say, though, that bug days will be a regular part of Plasma life again, with at least one such event hosted every release cycle.
Our long term goal is to get down to a stable 400-500 open defect reports, and I think that is achievable. We have worked through 600 reports in just 2 weeks, over half of them just this weekend. So it is possible.
The results of a clean bug database are that it becomes far, far easier for developers to identify what needs attention. It also helps our involved users know that, yes, we still have a pulse and do care and pay attention, something that sometimes gets missed.
I now have a nice parcel of "junior job" bugs and a handful of "critical issues for 4.8" in hand as a result of Bug Days ... and a really good feeling about things to boot.
Today has been relatively slow going as it isn't an official Bug Day so just a few showed up to do bug triage today. Quite promisingly, though, some people from the Bug Days showed up today again. I do hope all of them continue to be involved and help with the bug wrangling as their efforts were just fantastic this weekend.
I also set about to fix some of the older and more annoying issues in some of the more commonly used parts of Plasma Desktop. Many commits later, and many already-fixed (along with some won't or can't fixes, too), and the bug report count has dropped yet further. 4.8 is going to be a fantastic release.
Yesterday was really invigorating, as well: even more people showed up for day 2 than for day 1. That's understandable as it was the weekend. Together we mowed through large quantities of bug reports.
We also pulled together some Plasma bug hunting documentation for newcomers. It was very clear that handing out bugzilla account upgrades to those who took the time to show up was really worthwhile as well: it empowered people who may not have otherwise asked to help out, and boy did they ever.
I used to host bug days sem-regularly, but with project growth and life business they fell to the wayside. I'm happy to say, though, that bug days will be a regular part of Plasma life again, with at least one such event hosted every release cycle.
Our long term goal is to get down to a stable 400-500 open defect reports, and I think that is achievable. We have worked through 600 reports in just 2 weeks, over half of them just this weekend. So it is possible.
The results of a clean bug database are that it becomes far, far easier for developers to identify what needs attention. It also helps our involved users know that, yes, we still have a pulse and do care and pay attention, something that sometimes gets missed.
I now have a nice parcel of "junior job" bugs and a handful of "critical issues for 4.8" in hand as a result of Bug Days ... and a really good feeling about things to boot.
