lilypond-devel
[Top][All Lists]
Advanced

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

Re: 2.16.1


From: David Kastrup
Subject: Re: 2.16.1
Date: Wed, 24 Oct 2012 17:28:32 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "David Kastrup" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Devel" <address@hidden>
> Sent: Saturday, October 20, 2012 10:17 PM
> Subject: Re: 2.16.1
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> David,
>>>
>>> I see you've done a lot of moving updates into 2.16.1.  When do you
>>> expect to want a release for this?
>>
>> I've asked on the translator list whether they want to get something
>> translated from all the cherry-picking, and feedback is incomplete yet.
>>
>> -- 
>> David Kastrup
>
>
> How are we looking now?

git log --oneline --summary origin/stable/2.16..origin/translation

c78a460 Doc-es: update Changes.
 Documentation/es/changes.tely |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)
d8f3f53 Doc-es: update Rhythms.
 Documentation/es/notation/rhythms.itely |   74 +++++++++++++++++++++++++------
 1 file changed, 60 insertions(+), 14 deletions(-)
09f338e Doc-es: fix another xref.
 Documentation/es/notation/input.itely |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
f199e87 Web-it: update for 2.16.1 release
 Documentation/it/learning/fundamental.itely |    4 +-
 Documentation/it/learning/tweaks.itely      |   16 ++++----
 Documentation/it/notation/pitches.itely     |    6 +--
 Documentation/it/search-box.ihtml           |    2 +-
 Documentation/it/usage/lilypond-book.itely  |    2 +-
 Documentation/it/web/download.itexi         |    4 +-
 Documentation/it/web/introduction.itexi     |   55 ++++++++++++++++++++++-----
 7 files changed, 61 insertions(+), 28 deletions(-)
a072162 Doc-es: update Input.
 Documentation/es/notation/input.itely |  704 ++++++++++++++++++++++-----------
 1 file changed, 471 insertions(+), 233 deletions(-)
c4248fd Doc-es: fix xref.
 Documentation/es/notation/text.itely |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
f5c01cc Doc-es: update Tweaks, Expressive, Keyboards and Spacing.
 Documentation/es/learning/common-notation.itely |    9 ++--
 Documentation/es/learning/tweaks.itely          |   32 +++++++-------
 Documentation/es/notation/expressive.itely      |   54 ++++++++++++++++++++---
 Documentation/es/notation/input.itely           |   22 ++++-----
 Documentation/es/notation/keyboards.itely       |    7 ++-
 Documentation/es/notation/spacing.itely         |   29 +++++++-----
 6 files changed, 103 insertions(+), 50 deletions(-)
7df3f88 Doc-es: partial update.
 Documentation/es/essay/engraving.itely            |    2 +-
 Documentation/es/learning/fundamental.itely       |    4 ++--
 Documentation/es/notation/ancient.itely           |    2 +-
 Documentation/es/notation/changing-defaults.itely |    2 +-
 Documentation/es/notation/fretted-strings.itely   |    2 +-
 Documentation/es/notation/percussion.itely        |    2 +-
 Documentation/es/notation/pitches.itely           |    6 +++---
 Documentation/es/notation/simultaneous.itely      |   12 ++++++------
 Documentation/es/notation/vocal.itely             |    2 +-
 Documentation/es/search-box.ihtml                 |    2 +-
 Documentation/es/usage/lilypond-book.itely        |    2 +-
 Documentation/es/web/download.itexi               |    4 +---
 12 files changed, 20 insertions(+), 22 deletions(-)
2784264 Merge remote-tracking branch 'origin/stable/2.16' into translation
94e770a Web-fr: update searchbox
 Documentation/fr/search-box.ihtml |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
5198521 Doc-de: update commitsh strings to reflect status as up-to-date
 Documentation/de/essay/engraving.itely             |    2 +-
 Documentation/de/essay/literature.itely            |    2 +-
 .../de/extending/programming-interface.itely       |    2 +-
 Documentation/de/extending/scheme-tutorial.itely   |    2 +-
 Documentation/de/learning/common-notation.itely    |    2 +-
 Documentation/de/learning/fundamental.itely        |    2 +-
 Documentation/de/learning/preface.itely            |    2 +-
 Documentation/de/learning/templates.itely          |    2 +-
 Documentation/de/learning/tutorial.itely           |    2 +-
 Documentation/de/learning/tweaks.itely             |    2 +-
 Documentation/de/notation/ancient.itely            |    2 +-
 Documentation/de/notation/changing-defaults.itely  |    2 +-
 Documentation/de/notation/cheatsheet.itely         |    2 +-
 Documentation/de/notation/chords.itely             |    2 +-
 Documentation/de/notation/contemporary.itely       |    2 +-
 Documentation/de/notation/editorial.itely          |    2 +-
 Documentation/de/notation/expressive.itely         |    2 +-
 Documentation/de/notation/fretted-strings.itely    |    2 +-
 Documentation/de/notation/input.itely              |    2 +-
 Documentation/de/notation/keyboards.itely          |    2 +-
 .../de/notation/notation-appendices.itely          |    2 +-
 Documentation/de/notation/notation.itely           |    2 +-
 Documentation/de/notation/percussion.itely         |    2 +-
 Documentation/de/notation/pitches.itely            |    2 +-
 Documentation/de/notation/repeats.itely            |    2 +-
 Documentation/de/notation/rhythms.itely            |   49 ++++++++++++++++++--
 Documentation/de/notation/simultaneous.itely       |    2 +-
 Documentation/de/notation/spacing.itely            |    2 +-
 Documentation/de/notation/specialist.itely         |    2 +-
 Documentation/de/notation/staff.itely              |    2 +-
 Documentation/de/notation/text.itely               |    2 +-
 Documentation/de/notation/unfretted-strings.itely  |    2 +-
 Documentation/de/notation/vocal.itely              |    2 +-
 Documentation/de/notation/wind.itely               |    2 +-
 Documentation/de/notation/world.itely              |    2 +-
 Documentation/de/search-box.ihtml                  |    2 +-
 Documentation/de/usage/external.itely              |    2 +-
 Documentation/de/usage/lilypond-book.itely         |    2 +-
 Documentation/de/usage/running.itely               |    4 +-
 Documentation/de/usage/suggestions.itely           |    2 +-
 Documentation/de/usage/updating.itely              |    2 +-
 Documentation/de/web/download.itexi                |    2 +-
 Documentation/de/web/introduction.itexi            |    4 +-
 43 files changed, 89 insertions(+), 48 deletions(-)
e5a609e Merge branch 'translation' of ssh://git.sv.gnu.org/srv/git/lilypond into
288456f Doc-de: updating running manual
 Documentation/de/usage/external.itely      |    7 +-
 Documentation/de/usage/lilypond-book.itely |    2 +-
 Documentation/de/usage/running.itely       |  553 +++++++++++++++++++---------
 3 files changed, 384 insertions(+), 178 deletions(-)
236a505 Doc-de: update to extending
 .../de/extending/programming-interface.itely       |   12 ++--
 Documentation/de/extending/scheme-tutorial.itely   |   72 ++++++++++++++++----
 2 files changed, 63 insertions(+), 21 deletions(-)


I apologize for the long read.  I just wanted to point out just _how_
busy our translator team is, and usually their work is practically
invisible to normal development.

> There are a lot of changes in 16.1 compared with 16.0 - should it be
> released as a Release Candidate, do you think?  (NB - I'm not sure how
> this would be done at present, just musing).

To answer your question: no.  I have been rather conservative about code
changes: just stuff that has a really convincing balance between having
seen exposure in 2.17, not introducing new material, not being something
from which I expect problems after reviewing (yes, this is somewhat
unfair since it favors my own patches), not requiring convert-ly rules,
not changing semantics except where we need to fix a mistake in 2.16.0
that has not been there before...

Other than that, translation and documentation changes.  It is a bit sad
that after the big issue 2883 upheaval (it is on countdown, but that is,
at first, the "small" upheaval) the 2.16 documentation will not see
significant documentation backports and corresponding translations as
the documentors are tackling quite a few long-standing shortcomings.

But we need some motivation for releasing 2.18 at some point in the
future as well, and we have enough documentation work pending that we
should focus on moving forward.  If we get a load of backporting and
backtranslating volunteers, this might look somewhat different, but you
see above that the amount of work is not exactly to be sneezed at.

For the documentation, particularly translations, I think that "it
compiles" is the main hurdle.  Yes, there will be small problems and
inaccuracies, but people are better at correcting them on sight than
compilers are.

-- 
David Kastrup



reply via email to

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