Hi Martin, On Tue, Aug 28, 2012 at 8:33 PM, Martin Gräßlin <[email protected]> wrote: > 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?
This sounds indeed like a very good idea, and with a clear set of tests it is also not that difficult to achieve. With the 4.9.1 tagging around the corner (tomorrow IIUC: http://techbase.kde.org/Schedules/KDE4/4.9_Release_Schedule#Thursday.2C_August_30.2C_2012:_KDE_4.9.1_tagging) we should be able to work on this this weekend. Now hopefully we have enough testers around to do that, but I think it is possible. Who among the testers is running a git build and is available for that? Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
