[maemo-developers] QA process = bug fixing disincentive?
From: Frank Banul frank.banul at gmail.comDate: Sat Oct 31 21:26:47 EET 2009
- Previous message: QA process = bug fixing disincentive?
- Next message: QA process = bug fixing disincentive?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I just threw away 5 karma to make some changes (but I think worthwhile). I think the idea is that when there's many more users, 10 silly karma points will be nothing. Until then, have faith, or something like that. :) Frank On Sat, Oct 31, 2009 at 1:43 PM, Andrew Flegg <andrew at bleb.org> wrote: > Hi, > > After working 'til stupid o'clock last night on a new version of Hermes, today someone's found a bug which'll impact a small number of people. The fix is trivial. > > However, I find myself *not* wanting to fix it as it'll need to go through another round of testing. > > Although the principle of resetting package karma to 0 made some sense - as any change could fundamentally break the package - it's also true that a one-line change to a relatively mature package probably won't change whether it's optified; its power usage profile; its package description and icon etc. > > Perhaps there's an argument that some proportion of the karma earned should be retained, inversely related to length of time in -testing so far? > > Thoughts welcome. > > Cheers, > > Andrew > > -- > Andrew Flegg -- mailto:andrew at bleb.org | http://www.bleb.org/ > _______________________________________________ > maemo-developers mailing list > maemo-developers at maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers >
- Previous message: QA process = bug fixing disincentive?
- Next message: QA process = bug fixing disincentive?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]