[kde-promo] content needed for upcoming release announcement

Carl Symons carlsymons at gmail.com
Fri Jul 27 01:26:45 UTC 2012


Thank you, David. This will work well. It's not late.

Many thanks to the KDE Quality and Testing team.

Carl


On Thu, Jul 26, 2012 at 5:07 PM, David Edmundson
<david at davidedmundson.co.uk> wrote:
> On Tue, Jul 24, 2012 at 2:26 PM, Carl Symons <carlsymons at gmail.com> wrote:
>> The upcoming release announcement should include something about the
>> quality and testing project. It was mentioned several times in beta
>> and RC announcements and a lot of work went into it.
>>
>> Would someone here please write something about the program and the
>> results it produced? It doesn't have to be extensive nor grammatically
>> and otherwise perfect, but it should have interesting and pertinent
>> content. Please send to kde-promo at kde.org.
>>
>> The goal is to have the final version done by this Friday, 27 July so
>> that it can be translated. If someone can provide this to kde-promo by
>> Thursday, it can be included in the final version.
>>
>> Why was the project started?
>> What effect did it have on the Quality Team?
>> Were there any new contributors?
>> Were new people able to be effective?
>> What results were produced?
>>     Number of bugs found
>>     Number of bugs resolved
>>     Elimination of duplicates
>>     Ongoing contributors added
>>
>> Anything else that tells the story of what was intended and what was
>> accomplished.
>>
>
> Sorry I'm a bit late. I suck at writing, so edit anything.
>
> ----
> The KDE quality team was set up in April this year to maintain and
> improve the levels of stability of the KDE experience.
>
> One of the initiatives run by the KDE Quality team was to set up a
> more rigorous testing process for releases. Training was provided to
> volunteer teams of beta testers and several testing days were ran.
> Rather than traditional exploratory testing, testers were given
> special areas to focus on which had changed since previous releases.
> For several components full checklists of items to test were created
> and gone through. The team found many important issues early on and
> were able to make sure these were fixed.
>
> Special focus was made to identify any regressions from previous KDE
> releases and to prioritise fixing these in order to make sure KDE is
> always improving with each release.
>
> The testing team reporting over 163 bugs in the course of the beta and
> RC releases, many of which have now been fixed.
>
> ----
>
> Various more specific answers/facts/comments:
>  - 161 bugs opened officially by the people testing, but identifying
> all bugs opened by people involved in the testing is a lot higher.
>  - 71 of these "official" bugs were resolved
>  - Bugsquad is a slightly seperate topic, Mamarok has closed over 1300
> in general triage. With my Quality team hat on, triage/duplicate
> finding isn't really our job - however it's a lot of the same people
> involved and it has a lot of crossover.
>  - we got some new people helping..not many,
>  - this was an early testing of the testing...where we were focussing
> primarily on Plasma as a trail.
>
> Ping me if you need anything.
>
> Dave
>
> _______________________________________________
> This message is from the kde-promo mailing list.
>
> Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.


More information about the Kde-testing mailing list