Il giorno lun, 13/08/2012 alle 16.21 +0200, David Kastrup ha scritto: > If I handled it, I would try cherry-picking and praying. If your > proposal is in your comfort zone, I'd not mind letting you handle it. > However, I am not sure that the typical translator will understand what > is expected of him, so I would guess that you'd likely be working more > with commits on the main translation branch than your plan calls for.
I finally remember how we managed translation branch when I was translation meister (IIRC I did this for at least one of 2.10 and 2.12 releases): translation branch was no longer merged with staging and from master, but with and from the latest stable branch; then, when documentation changes or backports ceased on that stable branch or a limited goal of documentation to be translated was reached, translation changes were backported to master, and finally the translation branch got reset (deleted and recreated, actually) to master. As nobody seems to have merged translation from master since 952705bbbb000581a13836e6a733df04511e93c5, which precedes release/2.15.95-1, I favour this plan. John _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
