[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable

From: Joseph Rushton Wakeling
Subject: Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]
Date: Thu, 04 Oct 2012 19:17:05 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20121003 Thunderbird/15.0.1

On 10/04/2012 01:32 AM, Graham Percival wrote:
ok, so you won't mind volunteering to take care of this with your
personal email account.

Look, the whole point of what I was suggesting was this: that it would be useful for the Lilypond team to be _automatically_ notified when a downstream bug gets filed.

Not that anyone would have to take responsibility for triaging them or responding to them. Not that there would be any obligation to fix them. Just that there be a notification that this report has been filed downstream.

What does that change relative to now? Only that the community has received notice that these reports are there and that anyone on the mailing list has the _option_ to read them and respond -- as opposed to now where no one even knows they're being filed.

By putting it through one person and their private account, whether it's me or anyone else, all you do is create a bottleneck for that information. It doesn't make sense to have private individuals as the filter, because if those people have a busy period or fall under a bus or just bugger off, that filter turns into a block.

I'm perfectly happy to track downstream bug reports and write up something corresponding here if it seems relevant, but that's not solving the problem my suggestion was designed to solve -- that there is no _reliable_ channel via which downstream bug reports can propagate back to Lilypond. (Reliable, as in the sense of: the message doesn't get lost.)

If you don't see that problem as worth solving, well, it's your project. If you see the problems it creates as being greater than those it solves, that's your judgement. But I don't appreciate accusations of laziness or trying to foist work onto other people on the basis of a suggestion which was intended to help improve useful information flow to the project _without anyone having to do anything additional to what they're already doing_.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]