QA Testing for 4.9.1

[Martin Gräßlin]

Hi QA-Team,

there has been one thing with KDE's release process which I have disliked for 
quite some time: the fact that we release bugfix versions without any testing.

Most developers are using master and backport to the stable branch. This 
branch is hardly tested by anyone and I as a developer get feedback after the 
release that a fix is wrong or causes regressions.

Now with the QA team around I was wondering if we could do something about it. 
In the case of KWin we know exactly what went into the 4.9.1 release - 
everything is nicely documented in bugzilla [1]. Every bug should also have an 
instruction on how to reproduce.

So is there the chance that testers go through the list and verify that the 
fixes work as advertised?

Best Regards
Martin Gräßlin

[1] http://ur1.ca/a1pa0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-testing/attachments/20120828/7736656a/attachment.sig>