| Re: [translations] Git translation branch policy change: merge with and from stable/2.16 |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: David Kastrup <dak@xxxxxxx>
- Subject: Re: [translations] Git translation branch policy change: merge with and from stable/2.16
- From: Francisco Vila <paconet.org@xxxxxxxxx>
- Date: Mon, 1 Oct 2012 15:08:05 +0200
- Cc: John Mandereau <john.mandereau@xxxxxxxxx>, Translations list at lilynet <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q3Py005owqyDIFXyMP2qaEKkvOkw6CI4kELzbHoA3gk=; b=lvLui4f3aTqENLdkNQjzcYkeJ5r0BN+x8KGXiUcpkD/mk/TDqGMg4+c4phHo/fi/C0 mhXDA5BlqkAA+hLmRqcIywgtquRIQLg2z9eZyoSkDq+Hzx3C0UQDiraeqdpbgFmxb0bg 5/KafUK+ut/lWLU7vO54OG5uvkCMrN1Gwk8UAititghfzreG79NYYlLQhT/Y4l4YSqgU /p7heytiFqu7ewAAP+bdaADQjjeCVYAL8qjIGWCQ6ocYf0JnSoy1b07fXi3twEmX8MhE MZ1Xa31/29lIhhhnp+WF+i463YknuIbDVEC/WFz9oyjDRy7NF1jMt1lZWxwQsYdPMhaV eRxw==
2012/10/1 David Kastrup <dak@xxxxxxx>:
> Most of the already released material (in 2.17) flagged "Backport" is
> pretty obvious. But if you take a look at
>
> <URL:http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_17_0+OR+Fixed_2_17_1+OR+fixed_2_17_2+OR+Fixed_2_17_3+OR+Fixed_2_17_4>
>
> you'll see that there are a lot more one can feel rather ambiguous
> about: often they fix long-standing bugs, or make crucial performance or
> usability improvements. In the interest of a _stable_ release series,
> one should better leave them out. But that's a judgment call, and there
> is no really "correct" choice. So the "energy" that is needed for it is
> to muddle through with creating a release with known problems, creating
> something that is least likely to cause new regressions.
but code.google.com/p/lilypond/issues/list?can=1&q=label%3Dbackport+type%3Ddocumentation
is empty, so we translators should be able to go on working on 2.17.
We currently can't.
> I hope this gives you a better feeling for the path that seems sensible
> for the translation and documentation work to take.
We are stalled because there is no translation branch for 2.17 and all
released 2.17 versions include outdated translations which we can't
update. And pendant translation work for 2.17 is not going to stop
growing. Sorry, that can sound like selfish, I could be wrong, but
backport issues and blocking of 2.16 are irrelevant from the
translation point of view.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com