Graham Percival <gra...@percival-music.ca> writes:
> On Sun, Oct 25, 2009 at 02:16:27PM +0100, David Kastrup wrote:
>> Valentin Villenave <v.villen...@gmail.com> writes:
>>
>> > 2009/10/24 Frédéric Bron <frederic.b...@m4x.org>:
>> >> 1. can somebody feed the bug tracker with this bug?
>> >
>> > Sorry, I got lost in the discussion. Can you help me updating the bug
>> > report?
>>
>> Is it necessary to ask for bug report database updates? I filed several
>> bug reports to this list which as far as I can tell mostly got ignored,
>> to the degree where they did not only not get an answer, but also were
>> not filed into the database.
>
> It should not be necessary. The Bug Meister should respond within
> a week, either asking for more information, or informing you of
> the issue number. (ideally with a direct link, but a simple
> "thanks, added as 1234" is also ok)
>
> Of course, as with everything else in open source projects, the
> Bug Meister position is a volunteer job, so we take what we can
> get. If anybody thinks they can do a better job than the current
> person (including any of my jobs), I would encourage them to offer
> to take over the work. Or at least to work as an assistant.
The documentation states:
If you have discovered a bug which is not listed, please help us by
sending an input file which demonstrates the problem to the
bug-lilypond list. Unfortunately there is a strict “no top-posting”
check on gmane; to avoid this, add
> I'm not top posting.
(you must include the > ) to the top of your bug report.
Please DO NOT add bug reports directly to the bug tracker. Once an
issue has been added to the tracker, feel free to add more
information to that report.
It also gives elaborate details about what constitutes a good bug
report. There is no mention about what happens with bugs on the bug
report list. A reasonable expectation is that an automatism or
moderation stage will pick up a good bug report within a day. A
response time of a week is a sign that the mechanism is not working out.
Things like weeding out duplicates can happen at a slower time span. It
is also possible to put a bug into a database with a state "pending",
"unverified" or similar. That gives a better impression than a black
hole.
For one of the bugs I reported, a patch has been sent to the list
already by Patrick McCarty. Neither the bug report nor the patch have
seemingly been registered. The patch has not been merged or commented
on.
The exclusivity of bug tracker access does not apparently make a good
match with the current workflow of the development crew.
The results are not encouraging to contributors.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
