Hi, This might be understood as quite a controversial theme, but that's actually the reason why I'm writing it here. I've seen the progress in our last sprint and most of our delaying was caused by "trying to implement" some openQA test. This means we are fixing half of bugs we could. As I see it, there are two ways of step over this problem: 1. Minimize creating openQA tests to a.) features b.) important issues that are likely to break in the future [short to mid term] 2. Make creating openQA tests a piece of cake, maybe by introducing some Yast library, maybe by contributing to openQA to make it well understandable, well documented [mid to long term] We'll be, most probably, required to fix more bugs in Leap and SLE 12 SP1 in the near future. For that reason, I'd prefer #1 now, switching to #2 later. Is there any #3 or #4? Or maybe I'm just looking at it through different optics - maybe you even feel the bugfixing flow fast enough? Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org