[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Translations of the KDEPIM enterprise branches
From:       Chusslove Illich <caslav.ilic () gmx ! net>
Date:       2010-03-17 13:37:40
Message-ID: 201003171437.43624.caslav.ilic () gmx ! net
[Download RAW message or body]


> [: Albert Astals Cid :]
> I wouldn't say scripty is tied to two branches at all, why you say that?

On the one hand, I too reflexively broadened the scope of what Thomas
actually said he would like to have, to the this enterprise branch being
available for general translation. In that sense, by "Scripty system" I
meant the whole workflow around it: who in a team works on what branch, when
branches are switched, how back-porting/forward-porting is done, catalog
moves... This is what I meant by "tightly built around servicing two
branches".

On the other hand, even purely technically, Scripty lives withing the
branch. I.e. we don't actually have "Scripty servicing translation
branches", but simply "translation branches". This means that when we make a
change in trunk Scripty, and backport to stable Scripty, we would also have
to port to enterprise Scripty (and worse, to decide whether to port or not).

Still, if it's fine to have this enterprise branch as a "shadow" branch
unseen by teams in general, I suppose setting up Scripty on it is better
than any alternative.

-- 
Chusslove Illich (Часлав Илић)
Serbian KDE translation team

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]