Bug status

[Carl D. Sorensen]

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of address@hidden
> Sent: Tuesday, June 10, 2008 4:11 AM
> To: address@hidden
> Subject: bug-lilypond Digest, Vol 67, Issue 13
>
> Send bug-lilypond mailing list submissions to
>         address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.gnu.org/mailman/listinfo/bug-lilypond
> or, via email, send a message with subject or body 'help' to
>         address@hidden
>
> You can reach the person managing the list at
>         address@hidden
>
> When replying, please edit your Subject line so it is more
> specific than "Re: Contents of bug-lilypond digest..."
>
>
> Today's Topics:
>
>    1. Issue 437 in lilypond: alignAboveContext doesn't work as
>       expected (address@hidden)
>    2. Issue 65 in lilypond: \accepts has problems with \with
>       (lyrics   should be between staves)
> (address@hidden)
>    3. Issue 334 in lilypond: setting staff size not longer safe
>       (address@hidden)
>    4. Issue 213 in lilypond: progerror \bendAfter
>       (address@hidden)
>    5. Issue 313 in lilypond: missing warning for flat in changed
>       font (address@hidden)
>    6. Issue 588 in lilypond: Regression: LilyPond excessively slow
>       on        Windows XP (address@hidden)
>    7. Issue 498 in lilypond: completion heads loses tie
>       (address@hidden)
>    8. Issue 608 in lilypond: Completion_heads_engraver not working
>       correctly - ignoring note-events + wrong ties
>       (address@hidden)
>    9. Issue 607 in lilypond: Completion_heads_engraver not working
>       correctly - wrong application of ties
> (address@hidden)
>   10. Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn
>       (address@hidden)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 10 Jun 2008 02:34:16 -0700
> From: address@hidden
> Subject: Issue 437 in lilypond: alignAboveContext doesn't work as
>         expected
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; Format=Flowed
>
> Issue 437: alignAboveContext doesn't work as expected
> http://code.google.com/p/lilypond/issues/detail?id=437
>
> Comment #4 by v.villenave:
> Maybe we can keep it as an Enhancement request, indeed. I'm
> really not sure how/when/if it can be implemented, though.
>
>
> Issue attribute updates:
>         Status: Accepted
>         Labels: -Priority-Medium Priority-Postponed
>
> --
> You received this message because you are listed in the owner
> or CC fields of this issue, or because you starred this issue.
> You may adjust your issue notification preferences at:
> http://code.google.com/hosting/settings
>
>
> Message: 2
> Date: Tue, 10 Jun 2008 02:38:17 -0700
> From: address@hidden
> Subject: Issue 65 in lilypond: \accepts has problems with \with
>         (lyrics         should be between staves)
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; Format=Flowed
>
> Issue 65: \accepts has problems with \with  (lyrics should be
> between staves)
> http://code.google.com/p/lilypond/issues/detail?id=65
>
> Comment #3 by v.villenave:
> Great! It works.
>
>
> Issue attribute updates:
>         Status: Verified
>


Valentin,

I may be wrong (after all, you're the bugmeister), but I think you are using 
status codes differently than they have been used in the past.

It appears that you use "Verified" when a bug is fixed.  In the past, I believe 
that "Verified" means that the bug report has been found to actually be a bug, 
and that "Fixed" is used when the bug is no longer occuring.

This is almost a complete reversal of the meaning of "Verified", from "It 
really is a bug, and I've demonstrated it" to "The bug has gone away".

I'm not part of the bug team, so I have only minimal input to this issue, but I 
think it's a potential source of confusion for those who use the bug tracker.

Carl Sorensen