lilypond-devel
[Top][All Lists]
Advanced

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

Re: Any objections to branching off a stable branch for 2.20?


From: Phil Holmes
Subject: Re: Any objections to branching off a stable branch for 2.20?
Date: Tue, 18 Jul 2017 11:07:00 +0100

----- Original Message ----- From: "David Kastrup" <address@hidden>
To: <address@hidden>
Sent: Monday, July 17, 2017 7:14 PM
Subject: Any objections to branching off a stable branch for 2.20?



Currently there is a bit of a lull (not entirely graceful due to me not
keeping up with things all the best), so the time seems convenient.

There are a few "critical" bugs outstanding, the "Changes" document
should be reordered to be systematic rather than in reverse time order,
and I'd want to add a bit of syntactic Scheme and LilyPond sugar of the

\markup blabla = \markup \with-color #red \etc

variety in order to define named markup functions via \etc .  Basically,
this would split define-markup-command into a definition part called by

\markup blabla = ...

and a function part, say
(markup-lambda (layout props arg) (markup?)
  #:properties ....)

that can be generated by a \markup ... \etc expression or other means.

Basically, that's mainly for avoiding the current "ugh" of

blabla-markup = \markup ... \etc

that does not even work as (markup #:blabla ...).  I think.  This
syntactic addition is reasonably straightforward and limited.

Other things up for cherry-picking are documentation changes and their
translations.  Since translations usually are done in "bulk", it would
make sense to only translate stuff in the stable 2.20 branch in the
interregnum: that way the translation branch can be merged (rather than
individual parts cherry-picked) into the stable branch until the stable
branch gets released.

--
David Kastrup


No objections from me towards aiming for a 2.20 stable release.

--
Phil Holmes



reply via email to

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