[Top][All Lists]

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

Re: What is holding up 2.20 release?

From: Malte Meyn
Subject: Re: What is holding up 2.20 release?
Date: Tue, 17 Dec 2019 20:24:57 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0

Am 17.12.19 um 19:58 schrieb Jonas Hahnfeld:
3300acdd8d Issue 5532/1: \ottava doesn’t confuse ambitus
04a0052411 Issue 5532/2: add regtest

I think this is a fix for
a1bde20430 Issue 2575/1: Ambitus respects staffLineLayoutFunction
not yet in stable/2.20?

Not really. It fixes a bug I spotted when working on issue 2575 and which is independent from 2575:

\version "2.19.83"

\new Staff \with {
  \consists Ambitus_engraver
\relative {
  \ottava 1
  g'' f e d
  \ottava 0
  c b a g

3300acdd (issue 5532) does a check with scm_is_string which was changed to Text_interface::is_markup in f1649830 to prevent a regression (issue 5559). This change doesn’t have to be picked because 5559 won’t be picked.

09bc2e2ed7 Issue 5560: remove

should not be picked because it builds upon previous commits (for
example \henzeshortfermata)

I didn’t think of that when recommending to pick it, yes … And it’s not really a problem to have in 2.20 because any new scripts added in 2.21.xx won’t be added to 2.20 branch, will they?

I just realized how many new features are in master that will be in a stable release in 2.22.0 for the first time. I’m looking forward to 2.20 and 2.21 release because IIUC that means that release-blocking problems will be solved and 2.22 can follow soon :) Sadly, I have not found the time to learn enough about our build system to contribute (if there is still something left that blocks releases).

reply via email to

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