[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 824 in lilypond: Enhancement: anchors in the music stream
From: |
David Kastrup |
Subject: |
Re: Issue 824 in lilypond: Enhancement: anchors in the music stream |
Date: |
Fri, 23 Sep 2011 11:27:33 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Reinhold Kainhofer <address@hidden> writes:
> Am Friday, 23. September 2011, 09:31:00 schrieb address@hidden:
>> Comment #11 on issue 824 by address@hidden: Enhancement: anchors in the music
>> stream
>> http://code.google.com/p/lilypond/issues/detail?id=824
>>
>> address@hidden writes:
>>
>> No stable yet. Wasn't it "Fixed" when fixed in the development version,
>> "Fixed_xxx" when fixed in a certain release?
>
> Nope, fixed_2_15_xx is a tag that you should add to tell the testers which
> release to check. You are the only one who knows in which version the bug is
> supposed to be fixed...
>
>> Let me check the CG:
>>
>> * Fixed: a contributor claims to have fixed the bug. The Bug Squad
>> should check the fix with the next official binary release (not by
>> compiling the source from git). Owner should be set to that
>> contributor.
>>
>> Well, I claim to have fixed the bug. Nothing more, nothing less.
>> Working regtest is there, user level documentation is there, no word
>> from the bounty offerers. No bad conscience here on my part.
>
> You'll have to add fixed_2_15_xx, so the testers know when you supposed fixed
> the bug. Maybe this needs to be added to the CG more explicitly?
Since the issue tracker offers just "Fixed" as a default, I see no way a
contributor can really guess differently given the current state of
tracker and documentation.
--
David Kastrup
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, (continued)
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/21
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/23
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/23
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/23
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/23
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/25
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/25
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/25
- Message not available
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 2011/09/27
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Reinhold Kainhofer, 2011/09/23
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream,
David Kastrup <=
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Reinhold Kainhofer, 2011/09/23
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Graham Percival, 2011/09/23
- Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Graham Percival, 2011/09/23