On Tuesday, October 4, 2011 21:46:53 Sven Burmeister wrote: > Since we have to start somewhere, as a plasma dev, how do you feel about > prioritising regressions as soon as they are reported and fixing them ASAP, > i.e. before the next minor release at latest?
regressions where: master, stable branch, ..? how would they be identified? (e.g.: who would identify them, how would they be tagged, etc..) what is the definition of a regression? (i've had, on more than one occassion, a change in a feature described as a "regression" by a person who wanted it the old way.) with reasonable answers/definitions to the above, i can only say that regressions could be prioritized. there is no way, with a non-stable work force as in an open source project and the amount of work that we need to do elsewhere, commit to "by next minor release". in times past (and recent), our team has been quite capable of pounding out the bug fixes when the issues are well triaged and prioritized. so i don't think the issue is finding commitment from us for follow through, the issue is getting to a data set from which we can apply our commitment. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
