Re: 2.16.1

[David Kastrup]

Federico Bruni <address@hidden> writes:

> Il giorno 21/ott/2012 05:17, "David Kastrup" <address@hidden> ha scritto:
>>
>> "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.
>>
>
> Hi David,
>
> When did you ask? I may have missed your email..

I hope address@hidden is not a dead list (or did its list
server die, or is it "moderated" with no moderator ever approving
posts?).  At any rate, I sent several messages.  The first I can only
find in my mailing logs (Friday), but not in my mailing list archives.
Too bad.  Probably sitting in the translator list moderation queue.

I append the second one which presumably got a reply from Francisco only
because I replied to an old thread, thus directing a direct copy to him
as well.

The first mail mentioned the following presumably translator-relevant
output (since last translation merge)
address@hidden:/usr/local/tmp/lilypond$ git log 
origin/translation..origin/stable/2.16 --oneline Documentation
d47930b Doc: extend description of glissandi (2844)
6cb3cdb Web: Add Elysium to Easier Editing section
1141313 Doc: document \time command fully (2807)
dcddb2c inserted \clef "treble_8"
b2bdfeb Doc: delete obsolete para on two-pass spacing (2828)
6da27f9 Doc: Typos to LM - Fundamental and tweaks.itely
ba92a17 Doc: extend explanation of relative-includes (2558)
bcd8bd5 Doc: improve footnote documentation (2547)
a885534 Doc: clarify the use of a Scheme engraver.
4239aa2 Web: Removed note about MacOS Lion not supported
ac604de add website link to tunefl.com
629fc59 Doc: NR 3.2.1: clarify titles and \header blocks (2652)
5fd9cdc Fix over-long lines in glossary
44011e3 Issue 2760: CG wants all engravers to have double-quotes around them
6969857 Doc: MG: add incomplete dominant seventh chord (2749)
5b14676 Document "landscape" and "portrait" suffixes for paper size
35d565c Doc: standardise level 5 headings (2730)
c586c49 Doc: added link to conversion tools from Encore to lilypond enc2ly and 

I am not sure the Web entries need translations (or whether it was not
utterly stupid to cherry-pick them in the first place), but they _are_
compiled into local HTML and info information even if we don't display
them prominently on the live web pages.

I have no really good idea about the changes document.  I lean to
pasting a single link there to our bug tracker, listing Fixed_2_16_1
labels.

> I think that all translators should update the inaccuracies in LM.
> I'll try to do it today, even if I'm abroad and with a Windows laptop.

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [translations] Git translation branch policy change: merge with and from stable/2.16
>
>
>
>
> Date: 
>
> Sat, 20 Oct 2012 12:44:29 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)
>
>
>
>
> If it is ok with people, I'd propose the following course in order to
> get the ball rolling again:
>
> I'll merge stable/2.16 into translation.  That should be unproblematic.
> Then I'll merge translation into staging.  This will require a bit of
> cleanup and conflict resolution.
>
> I am willing to take care of that and of the translation merges into
> staging when translation is still based on stable.  Since one purpose of
> getting staging up to date with regard to translations is to be able to
> do extensive convert-ly work, the merging might be a bit tricky until
> things move over completely.
>
> I am not sure when translators will want to move their focus to master
> rather than stable again: it might be possible to create a branch
> translation-stable for working on stable branch translations, but I
> would like to phase out stable branch work eventually and so a separate
> translation-stable can still be left for a time when we feel we really
> need it.  Probably cherry-picking will be enough if commits for
> unstable-only material are kept separate well enough.
>
> At any rate, with this plan it is more or less up to the translators to
> decide when they think 2.16.1 is ready.  There is not much I
> cherry-picked into the stable branch since the last translation merge,
> and I'd not like to wait much longer than a week for 2.16.1 in
> consequence, but 2.16.2 will likely take quite longer.
>
> People fine with that?
>
> -- 
> David Kastrup
>
> --- End Message ---

-- 
David Kastrup