Re: Git translation branch policy change: merge with and from stable/2.16

[Francisco Vila]

2012/9/13 John Mandereau <address@hidden>:
> I think the message that started this thread stated it clearly: "From
> now on, translation branch at the repository on Savannah should no
> longer be merged with master and into staging; instead, it should be
> merged with stable/2.16."

Well, right.

>>  but now I have a request. The translation
>> branch is still in 'stable' status. I think it should be kept so for a
>> while, i.e. not to merge master into translation until a new 2.16.x
>> stable is released. I believe this is the path to go because no
>> translation/stable branch has been created, therefore if we want to
>> sync our translations to master, we have no way of knowing what to
>> translate and what not to.
>
> Creating a translation/stable branch is easy, but I don't know how
> translators would be comfortable with switching between two branches for
> translation work (maybe I wouldn't if I worked on translations myself).

We have to choose between fussing around with switching branches or
fussing around with guessing what to translate for stable only. The
former is very difficult but feasible, the latter is almost impossible
is master gets merged on translation.

>> After next 2.16.x, we can merge master into translation and go on with
>> translation of development branch.
>>
>> Right?
>
> You mean 2.16.1, don't you?

Yeah,

> The probable frequence of 2.16 releases makes this sound like a good
> idea.
-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com