Re: Please pull git-po master branch

From: Thomas Rast <trast@inf.ethz.ch>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Thomas Rast" <trast@student.ethz.ch>,
	"Ralf Thielow" <ralf.thielow@googlemail.com>,
	"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>,
	"Byrial Jensen" <byrial@vip.cybercity.dk>,
	"Vincent van Ravesteijn" <vfr@lyx.org>,
	"Marco Sousa" <marcomsousa@gmail.com>
Subject: Re: Please pull git-po master branch
Date: Thu, 3 May 2012 09:49:09 +0200	[thread overview]
Message-ID: <874nrxwvpm.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CANYiYbH+N3k_=FWyeS_HfBWSBeBdOUqW5qrHFe=qV4ECtYABpA@mail.gmail.com> (Jiang Xin's message of "Thu, 3 May 2012 12:31:57 +0800")

Jiang Xin <worldhello.net@gmail.com> writes:

>  * Pull requests with a initial XX.po (untranslated) and updated TEAMS file
>    will not merge to the master branch, but merge to a work in progress
>    branch, such as WIP/XX.

Please don't take my complaint as a request to completely over-engineer
the process, that will just make it more work for everyone and scare
away potential translators.

I think it's sufficient to

* not put _completely new_ translations in maint

This one is actually very similar to the rule for code: maint does not
usually get new features either.  (The only exception I'm aware of is
when maint needs to learn to "speak" a new format introduced in newer
versions.)

* not submit pull requests late in the rc phase

With a similar reasoning.  Because there are usually several -rc tags,
doing this will ensure that the new translations get fairly wide
exposure with interested developers.

So more or less what we do for code, too.

Of course there's the flip side that I should have watched i18n more
closely (as evidenced by me being a loudmouth now).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch