New bug priority: postponed

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

New bug priority: postponed

Graham Percival-2
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 next big
Low: might be fixed in one or two stable releases
Postponed: fix would be difficult without major restructuring of the
lilypond internals, and/or there is no developer actively working in
this area.  IMO, all ancient notation bugs qualify for this, as do
esoteric collision bugs.


Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: New bug priority: postponed

Han-Wen Nienhuys-3
Sounds good.  You have to be careful that the postponed category
doesn't become a dumping ground though. a

2007/3/28, Graham Percival <[hidden email]>:

> 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 next big
> Low: might be fixed in one or two stable releases
> Postponed: fix would be difficult without major restructuring of the
> lilypond internals, and/or there is no developer actively working in
> this area.  IMO, all ancient notation bugs qualify for this, as do
> esoteric collision bugs.
>
>
> Cheers,
> - Graham
>
>
> _______________________________________________
> lilypond-devel mailing list
> [hidden email]
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>


--
Han-Wen Nienhuys - [hidden email] - http://www.xs4all.nl/~hanwen


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: New bug priority: postponed

Graham Percival-2
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't think it's bad to have a dumping ground -- we just don't have
enough developer resources to fix every bug and implement every feature
request.  With a "dumping ground", users (and potential bug-fixing
developers) will get a more realistic idea of the devel team's abilities
and limits.

Cheers,
- Graham


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: New bug priority: postponed

Juergen Reuter
In reply to this post by Graham Percival-2

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 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 next big
> Low: might be fixed in one or two stable releases
> Postponed: fix would be difficult without major restructuring of the lilypond
> internals, and/or there is no developer actively working in this area.  IMO,
> all ancient notation bugs qualify for this, as do esoteric collision bugs.
>
>
> Cheers,
> - Graham
>
>
> _______________________________________________
> lilypond-devel mailing list
> [hidden email]
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: New bug priority: postponed

Bugzilla from kevin@kelphead.org
In reply to this post by Graham Percival-2
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 prioritize low
priority items which are not close to being fixed, but it may not be a
big waste of time.

Of course, with open source software, anyone can offer a fix of a low
priority or postponed item at any time.

I don't think postponed is desperately, but it probably doesn't hurt
to have it, as long as you don't need to spend too much time
categorized each bug.

http://en.wikipedia.org/wiki/Agile_programmingp

Graham Percival <[hidden email]> writes:

> 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't think it's bad to have a dumping ground -- we just don't have
> enough developer resources to fix every bug and implement every
> feature request.  With a "dumping ground", users (and potential
> bug-fixing developers) will get a more realistic idea of the devel
> team's abilities and limits.
>
> Cheers,
> - Graham
>
>
> _______________________________________________
> lilypond-devel mailing list
> [hidden email]
> http://lists.gnu.org/mailman/listinfo/lilypond-devel


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel