Re: spacing/breaking issue [time-sensitive]

[Graham Percival]

On Mon, May 31, 2010 at 4:36 PM, Kieren MacMillan
<address@hidden> wrote:
> MAO MAO-ING MAO, can we please resolve these spacing issues ASAP?

At the risk of making a crude masturbation joke, if I could wave a
magic wand to fix stuff, I'd be waving my wand all day and night.


> Sorry for the rant -- I blame the deadline pressure -- but it really is a bit 
> ludicrous, and does not give Lilypond the best possible chance of impressing 
> anyone out of the box. If this issue isn't on your "critical 2.14-killer" 
> list, it should be.


For the record, there are NO KNOWN BUGS with the new spacing
algorithm.  Every single spacing regression bug that has been sent to
bug-lilypond has been fixed.
** nb: actually, this might be incorrect.  There's about 5-10 bugs
that were sent to bug-lilypond, but for which nobody has processed
them.  One of those might contain a nicely-written bug report with a
Tiny example which demonstrates this problem.  So rather: every single
spacing regression bug that was entered to the issue tracker has been
fixed.


Because of our recent discussion about contributors getting started,
I've spent an hour rewriting the CG chapter about Issues and the
website "help us" page.  Hopefully in a few weeks I can start
recruiting new people to join the Bug Squad -- perhaps even you? this
requires absolutely zero interaction with the source code and
compilation, after all -- so that we won't lose good bug reports.  (or
even non-good bug reports)

Hopefully after the deadline is over, you could create a tiny example
of your problem and report it as a bug.  Or, since Joe doesn't seem to
be very picky about spacing bugs, and is probably willing to assure
you that he will not show copywritten material to anybody else, you
might be able to send your current score directly to him.


But I want to be absolutely clear that I can do is organize the bug
reports and attempt to herd the cattish developers.  If I have no
reports (again, leaving aside the lost ones), I can't try to
manipulate any developers into working on those problems.

(with regards to the "lost" bug reports: again, all I can do is to
organize people willing to work on bugs.  If we have so few volunteers
offering to help organize bugs that we can't process all bug reports,
then we'll obviously lose bug reports.  *shrug* )

Cheers,
- Graham