[Top][All Lists]

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

Re: Lilypond code/feature freeze for 2.12

From: Han-Wen Nienhuys
Subject: Re: Lilypond code/feature freeze for 2.12
Date: Mon, 22 Sep 2008 12:49:44 -0300

I'd drop

 teams have also been working hard everywhere in the world:

 Since we can't decide
 which ones you'll enjoy the most,

- Page-breaking has been improved with a new function designed to help
 with the production of books with many pages or lots of text, and the
 manual control of page breaks is now possible at the top level.

I was referring to Joe's page breaking, which will put page breaks in
sane places for multipage pieces, but I was mistaken.  We shipped it
in 2.10.  I'm not sure if we more earthshattering changes beyond gdp
and skylining.

On Mon, Sep 22, 2008 at 12:33 PM, Trevor Daniels <address@hidden> wrote:
> Han-Wen Nienhuys Monday, September 22, 2008 3:50 PM
>> On Mon, Sep 22, 2008 at 5:53 AM, Valentin Villenave
>> <address@hidden> wrote:
>>>> I've read plenty of release announcements, but my reaction is
>>>> different -- marketing make feel greasy and icky.  I had five
>>>> years of training to be as precise as possible in my analytic
>>>> philosophy degree; I hate empty phrases like "50 new features".
>>> Oh, come on.  I hate marketing as much as you do, but we are not
>>> selling anything to people who don't need it.  We've had this debate
>>> many times, and you know how important I think it is to raise people's
>>> enthusiasm in such projects.
>> I think the release notes should both be enthusiastic, but also as
>> short and factual as possible. In this draft, I'd fold
>> - Our online documentation is now generated by a new system that
>> makes it simpler to browse... and much better-looking.  It has never
>> been easier to get started with 'Pond!
>> into the doc item, and the doc item could be shorter.
>> - This release contains vastly improved collision detection.  Many
>> graphical score objects will avoid overwriting each other, leading
>> to far fewer manual tweaks.
>> I think this is a good point, but it should be more specific: how is
>> it improved, what collisions are prevented?
>> as a matter of style, good things come in threes, so I'd add one other
>> highlight. I'd also mention the page breaking improvements.
> How does the attached version look?
> Trevor

Han-Wen Nienhuys - address@hidden -

reply via email to

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