Jonas Hahnfeld <[email protected]> writes: > Hi David, > > Am Donnerstag, den 06.02.2020, 00:44 +0100 schrieb David Kastrup: >> Whatever else may be on the plate, the immediate problem to be put >> behind us right now is the release of 2.20. > > fantastic! > >> I put specifically the >> translation team and Werner into Cc. The translation team should check >> what changes of the recent release of 2.19.84 they still need to get >> track of. >> >> Werner basically is the person most affected by changes I have not yet >> cherry-picked because of problems, changes that likely would be a good >> idea to have in 2.20. >> >> Those are his extensive indexing review, and reworks of several >> examples. The indexing review is hard to apply to the by now >> significantly from master diverged stable/2.20, and with the reworks of >> the examples I am not sure whether they need to be accompanied by >> changes to the lilypond-extra archive. At some point of time, there has >> been such a requirement; I was not sure whether it persisted. If I am >> assured that this is either not an issue, or that lilypond-extra will >> get the necessary treatment until we can release 2.20 (hopefully in a >> week or so), I can do the required cherry-picking myself. >> >> So let's make sure we get our last ducks in a row for closing that >> long-awaited chapter. > > Do you still plan to pick the doc updates you mentioned in your last > email? See my response for how to do so without too much pain: > https://lists.gnu.org/archive/html/lilypond-devel/2020-02/msg00032.html
Ah right, the command line stuff. I'll take a look. But I'd really need feedback about Stockhausen et al from whoever knows how the images make it into the doc and/or web pages on what would be the right way to process/include them these days. -- David Kastrup
