76
edits
Changes
Jump to navigation
Jump to search
Line 40:
Line 40: + +
→Priorities
:This is an excellent starts. I would probably go as far as saying that new features should never be blockers. One problem that I see in many bug systems is that priorities are rarely assigned consistently. Not only because of lack of clarity of the meaning but often just because no one triaged priority. Who is in charge of priority triaging? Reporter, maintainer, release manager? -- marco
:This is an excellent starts. I would probably go as far as saying that new features should never be blockers. One problem that I see in many bug systems is that priorities are rarely assigned consistently. Not only because of lack of clarity of the meaning but often just because no one triaged priority. Who is in charge of priority triaging? Reporter, maintainer, release manager? -- marco
::''In my experience, bug priorities in dev.laptop.org have meant little more than 'I want you to read this bug soon' or 'Read this at your leisure'. In particular, there has been little correlation between bug priorities and release priorities and between bug priorities and the state of individual developer's work queues. Also, displays of bug priorities fail to record higher-order project state information like the derivative (rate of change) of the priorities function and the interference rate (i.e. how much work is being done which is not recorded in the bug tracker). We should strive to do better.'' --[[User:Mstone|Mstone]] 18:36, 15 May 2008 (UTC)
===Verify===
===Verify===