Reinhold Kainhofer <reinh...@kainhofer.com> writes: > Am Friday, 23. September 2011, 09:31:00 schrieb lilyp...@googlecode.com: >> Comment #11 on issue 824 by d...@gnu.org: Enhancement: anchors in the music >> stream >> http://code.google.com/p/lilypond/issues/detail?id=824 >> >> lilyp...@googlecode.com 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 _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
