Re: 2.18

[Janek Warchoł]

Hi,

2013/4/14 David Kastrup <address@hidden>:
>
> Ok, nobody including myself bothered reverting
>
> commit 88d306d9c5666b5ade4a136df29cca19c5ff5ed7
> Author: Mike Solomon <address@hidden>
> Date:   Sat Apr 6 09:54:58 2013 +0200
>
>     Break slurs between alternative endings in repeats; issue 1698.
>
>     Create new event-types BreakPhrasingSlurEvent BreakSlurEvent,
>     and a music-function \free so that users can create them.
>     Create these event-types in the volta-repeat-iterator to break
>     slurs between alternatives in a \repeat volta structure.
>
>
> in time for 2.17.16 and it is clearly unfit for releasing in 2.18 (new
> functionality, new interfaces, change of behavior without significant
> exposure, no documentation).  I propose reverting it now and move it
> along with all its related followup and refinement work into 2.19 once
> 2.18 is released.

I can accept that.

> the rest positioning really needs as much
> feedback as possible regarding correct behavior in the standard staff
> case, and desirable behavior in the tablature and drum staff cases.

I'll comment on it as soon as i have a testfile that covers all cases
to analyze.  Of course i can write this testfile myself if necessary,
but it will take me some additional time; it would be great if you
made it as you're obviously more familiar with the issue.

> Why these two changes?  Because both are egg-in-our-face material
> affecting the whole online presentation of LilyPond and our showcase
> material in the introductory sections.  I'd hate to see the current
> behavior define our public presentation of "stable" for the next year to
> come.

I assure you that issue 2658 is annoying me at least the same as you.
It's hideous.
But apparently we all lived with it for many years...


2013/4/14 Keith OHara <address@hidden>:
> David Kastrup <dak <at> gnu.org> writes:
>
>> Ok, nobody including myself bothered reverting
>>     Break slurs between alternative endings in repeats; issue 1698.
>> in time for 2.17.16 and it is clearly unfit for releasing in 2.18 (new
>> functionality, new interfaces, change of behavior without significant
>> exposure, no documentation).
>
>> Two things I consider important for 2.17.17 are the strokeadjust changes
>> for PostScript output, and the vertical rest positioning.
>
> Is this parody?  April Fools Day was two weeks ago, David.

Indeed, i consider strokeadjust changes as definitely inappropriate
for 2.18 - it's a change of how every single output file will look
like, and thus i think it should have at least two months of exposure
before being added to a stable.  Especially since it was already
discovered that the output gets worse in some cases.

best,
Janek