Hi David,
Am 31.10.2017 um 23:07 schrieb Flaming Hakama by Elaine:
From: Urs Liska <li...@openlilylib.org <mailto:li...@openlilylib.org>>
To: lilypond-user <lilypond-user@gnu.org
<mailto:lilypond-user@gnu.org>>
Subject: LilyPond blog
"Scores of Beauty" (http://lilypondblog.org) is LIlypond's
semi-official community blog, ...I urgently suggest that people
decide to contribute to it, and in particular I would be happy if
someone could step up and take over some editorial responsibility.
...
Best
Urs
Having volunteered for this, I figured I could try a stab at writing a
preliminary "what's new in 2.20" type of post in advance of the release.
That sounds good. We'll have to see how that plays out and whether it
will be good to publish that *before* the release or rather *write* it
beforehand and publish it immediately after a release. My gut feeling
says the latter would be better, but if you have a good idea how to
"package" such a text I'm open for anything.
What is the best way to find out what has been accomplished since 2.18?
What you will probably want is
http://lilypond.org/doc/v2.19/Documentation/changes-big-page.html
which lists the changes between the latest 2.19 release and 2.18 from a
larger high perspective, i.e. when the developers found it suitable to
explicitly mention a change in the change log.
This is probably what people want to know.
I do have access to the issue tracker
https://sourceforge.net/p/testlilyissues/issues/
But I'm not sure how it is organized. Perhaps the new release
consists of the 42 issues tagged as "Open (Patch)"?
Or, would I need to look for issues that are closed, status fixed, and
anything newer than the date of the 2.18 release?
*Actually* what you need is status "verified", and using
status:Verified labels:Fixed_2_19
as filter will give you all the issues that have successfully been
closed in the 2.19 line.
But this shows 3721 results and is pretty fine-grained and not much more
manageable than the Git log that Karlin referred to. *If* you want to
inspect that path (or at least start with it to get an idea about it)
you will notice the relation between the git log and the issue list - as
it is commonly expected that commit messages include references (usually
already in the title) to an issue tracker item.
But as I said, for the purpose of a "consumer-level" article about the
improvements the changes document is probably the appropriate reference.
Best
Urs
Thanks,
David Elaine Alt
415 . 341 .4954 "/Confusion is highly underrated/"
ela...@flaminghakama.com <mailto:ela...@flaminghakama.com>
self-immolation.info <http://self-immolation.info/>
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
