| [translations] Re: Current state of release planning. |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: David Kastrup <dak@xxxxxxx>
- Subject: [translations] Re: Current state of release planning.
- From: John Mandereau <john.mandereau@xxxxxxxxx>
- Date: Mon, 13 Aug 2012 14:22:42 +0200
- Cc: lilypond-devel@xxxxxxx, translations@xxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:x-mailer:mime-version:content-transfer-encoding; bh=wTkSduUhxoLBcOdUOqn84UWVG/VALaveN5ZInrsIHxg=; b=SvWdJVK288JOnXfgWWxThqzZ2lnUzG46YvE+S6CJawovhJ0EaqQPdNt0JS2y+Tam9Z AvLV2yorWrmH/3IjXtAIWEfBC2GmzTpeIRmTIwdH3pbrKwA7TWWxxkVU0dknVPBPpUjR 3YXKe8nkpsoOUOF3p4ByMHVBVTjTULgyuVg2fTeJ3i4/sz1Hgty1o/3XncBS+X7phice zG/7Co2xwxEvF2HmOuOZLZtCFlkzPRs0d0Aymf84yNeQRK+BTRcdnnoqCUfRlg/ghDL7 QoONE8QTjWVfqVyKSvWO4WWr4+c0WND5ubyghN9535Per8E5XUzLl7zMxII+mPsj9ZNW 4QNg==
Le lundi 13 août 2012 à 10:55 +0200, David Kastrup a écrit :
> I haven't really tracked translations so far, so my own level of
> suitability here is pretty close to zero, modulo non-task-specific
> computer expertise (which some people deem sufficient for making me
> useful for Windows support, a system I have successfully avoided for
> decades). In other words, I'd be happy to delegate, but we are not
> likely to have the help of patchy-staging for it. Stuff has to be
> well-tested.
Well, the first instance of Patchy's translation branch build I put up
on Grenouille was broken (it tried to create and build a fast-forward of
master from translation), I think I fixed it (as well as the general
case of building any branch other than staging), and last build seemed
to work, I'll likely push Patchy changes on Wednesday; this periodic
build should give an additional hint about the state of translation
branch.
If I handled backporting translation updates, I would create
translation-2.16 branch on central repository on Savannah, with the
policy to allow history rewriting on that branch, I would rebase it on
stable/2.16, ask translators to work on a separate branch checked out
from stable/2.16 (but that would never get pushed except something like
dev/translator-name), apply patches from emails or cherry-pick from
dev/translator-name on translation-2.16, build this branch with
Patchy and if Patchy is successful fast-forward stable/2.16 to
translation-2.16, and repeat the process once (or if necessary twice) a
week.
> I am clueless in that area, so it will be good if you kept track of what
> was required here.
Paco has announced to be on vacation and mostly offline until Friday, so
Jean-Charles and I took this task -submitting to the TP) over from him,
to give translators roughly two weeks for submitting POs for 2.16.
> I think we have a reasonable chance to be in the
> same room with Graham when releasing 2.16 if things go well.
In the meantime, cross fingers, and more importantly let's trim hard on
those bugs :-)
Best,
John