I like the agile programming or extreme programming model that you
work on the items at the top of the list, and don't worry about the
items near the bottom of the list.
The low priority items will be fixed when all the items above them are
finished. It is probably a waste of time to precise prio
FYI: There are vague chances, that in 2008 I will be able to schedule a
little bit more of my time for lilypond again. ;-)
Greetings,
Juergen
On Wed, 28 Mar 2007, Graham Percival wrote:
About six months ago, there was discussion about a priority level below
"low"; at the time I argued again
Han-Wen Nienhuys wrote:
Sounds good. You have to be careful that the postponed category
doesn't become a dumping ground though. a
Well, in some ways the "low" category is already a dumping ground. I'd
rather have a dedicated label for such things, instead of everything
being "low".
I don'
Sounds good. You have to be careful that the postponed category
doesn't become a dumping ground though. a
2007/3/28, Graham Percival <[EMAIL PROTECTED]>:
About six months ago, there was discussion about a priority level below
"low"; at the time I argued against it. I've now changed my mind and
About six months ago, there was discussion about a priority level below
"low"; at the time I argued against it. I've now changed my mind and
added a "Priority-Postponed" tag.
Here's my interpretation of the bug priorities:
High, Regression: fix within one or two releases
Medium: fix before ne
