bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 1273 in lilypond: Woodwind Diagrams lead to Ghostscripterror i


From: Graham Percival
Subject: Re: Issue 1273 in lilypond: Woodwind Diagrams lead to Ghostscripterror in latest git
Date: Mon, 27 Sep 2010 18:29:46 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On Mon, Sep 27, 2010 at 06:17:42PM +0200, Valentin Villenave wrote:
> On Sun, Sep 26, 2010 at 7:10 PM, Graham Percival
> <address@hidden> wrote:
> > I know that we're not meeting that goal, but a few people are
> > still learning the ropes.  Certainly by the end of this year, I
> > want the Bug Squad to be fulfilling that job.
> 
> Another think we could do before a stable release is check every
> opened issue to verify that some bugs haven't been fixed (or made
> worse) without anyone noticing. I did so with 2.11.47 shortly before
> 2.12 was released.

That's been in the works, but no point adding more work to the bug
squad when it can't handle the current load.

But we don't want a splurge of updated bug reports, because that
makes developers sigh and delete an entire mailbox without reading
it.  We want one updated issue each day.  If there's anything
unclear, we can get it sorted out with developers.  That won't
happen if you do 10 each day, because it'll get lost in the noise.

Yes, it will take about 2 years to process the entire archive.
That's fine... that's the right kind of timeframe to begin the
process again.

> (I'll try and have a look in October, when .14-stable is branched.)

Yeah... or, you know, just _maybe_... you could actually do your
BLOODY 15 MINUTES on your day?!?!

We currently have at least 2 "abandoned bug reports".  They've
been abandoned for days.  One is a completely valid enhancement
request.  Now, I don't care about microtonal music at all, but I
don't enjoy looking like an idiot after I made such a big deal to
them about following proper enhancement-request procedures and
then having nothing happen.  But hey, that's life.  I can take it.
The other issue?  Looks like a completely valid Critical
regression to me.  You know, the kind of reports that we REALLY.
SHOULD. NOT. LOSE ?  especially just before a stable release?


*sigh*

Maybe we _should_ start the issue-revisions now anyway, just to
remind people that there's always work to do, so if you said you'd
spend 15 minutes working on this, then bloody well *spend* that
time.

- Graham




reply via email to

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