|
From: | Urs Liska |
Subject: | Re: LilyPond blog |
Date: | Tue, 31 Oct 2017 23:31:25 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
Hi David, Am 31.10.2017 um 23:07 schrieb Flaming
Hakama by Elaine:
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 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.
*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
|
[Prev in Thread] | Current Thread | [Next in Thread] |