| Re: [translations] Git translation branch policy change: merge with and from stable/2.16 |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
Le 01/10/2012 15:08, Francisco Vila disait :
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.
Here is a list of commits touching /Documentation without any change to
the code base. They are mostly typos or removals of bad info or
improvements. I think all of them should be part of any 2.16.
0a12e59b93bceea2c94c61e5c35b17cd88fb6d8f (David Kastrup)
Issue 2760: CG wants all engravers to have double-quotes around them
e15e0d22810063b79da891bbf472ecc39d09c02c (Federico Bruni)
Web: add W3C properties of border-*-radius after vendor ones (2784)
d3b8117dc5f12634c7a093955d3b32f66ce26b5e (Trevor Daniels)
Doc: NR 3.2.1: clarify titles and \header blocks (2652)
6ce800445921f6f32eeb60bfbf7acf1cdba2f9c1 (Janek Warchoł for Rodolfo
Zitellini)
add website link to tunefl.com (2660)
5fed61cb3b4f254cac376555734bcf748573ea66 (Francisco Vila)
Doc: clarify the use of a Scheme engraver.
9d074d78d7c25852afa87005e21c118630f4f83b (Phil Holmes)
Hard-coded version numbers updated
2cc80f28ca3d5cd956201c6f3bdc25ddeef09b89 (Werner Lemberg)
[doc] Improve example for unpure-pure-container.
3cd24002639b7b48a9f0c7245101bdb721ce21c0 (John Mandereau for Werner Lemberg)
Add support for Cyrillic in Texinfo/TeX
e5cee7b0d83b2a4f5be602e02aed91a498e3fcdb (James Lowe)
Web: Removed note about MacOS Lion not supported
a9a451e2316c2e94815e33d51eb42eaae3649384 (David Kastrup)
Issue 2826: Let do_yyparse return a value rather than going through
parseStringResult
4c33251402e969f15fa796363fe646dff07b2798 (James Lowe)
Doc: Typos to LM - Fundamental and tweaks.itely
0fc20deb5b706498d328b1c69836a44a00abec9d (Trevor Daniels)
Doc: improve footnote documentation (2547)
6f44845de9ce94edf96aac8a4d0c4498eeb35360 (Trevor Daniels)
Doc: delete obsolete para on two-pass spacing (2828)
e8f2efa8e3cc826f65223c931e42283d973831b5 (Francisco Vila)
Doc: fix small inaccuracy in notation manual, chapter Chords.'
80ac25965335ba51ace93fe478ce7f7907e4df91 (Trevor Daniels)
Doc: extend explanation of relative-includes (2558)
f8710cbaf9563515cf383c658a534b5c902897a1 (Trevor Daniels)
Doc: document \time command fully (2807)
9e605a1bb6644d89cf110f20cb6d46bb0339fca7 (James Lowe)
Web: Add Elysium to Easier Editing section (2871)
Cheers,
Jean-Charles