bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font


From: Graham Percival
Subject: Re: Issue 1752 in lilypond: redesigning G clef in our Feta font
Date: Tue, 26 Jul 2011 13:33:52 -0700
User-agent: Mutt/1.5.20 (2009-06-14)

On Mon, Jul 25, 2011 at 04:36:47PM -0600, Carl Sorensen wrote:
> On 7/24/11 5:43 PM, "address@hidden" <address@hidden>
> wrote:
> 
> > (obviously) I don't like this solution because it makes my work lie on a
> > shelf for a few months and do nothing but collect dust.
> 
> This proposal was based on Graham's assertion that 2.16 is 10 days away from
> release, so your new clef would be 10 days away from being in 2.17.

Correction: if there are 0 critical issues, the first release
candidate for 2.16 will happen in 6 days.  However, I currently
see 2 Critical issues.

> If we need a shorter-term solution, and having had Graham take back his
> Critical Regression brain fart, I'd say we go ahead and push the changes,
> and then James will either have to use the current version, or maintain a
> patch to the font.

I think this is the best solution as well.  It might be nice to
add a bit more documentation about how somebody who really
disliked the new font could go about replacing it, but we've never
viewed documentation as holding back programming work in the past.
So go for it.

Cheers,
- Graham



reply via email to

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