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

List:       kde-i18n-doc
Subject:    Re: Translations for upcoming 4.11.x and 4.12.x
From:       "Yuri Chornoivan" <yurchor () ukr ! net>
Date:       2013-10-21 16:44:43
Message-ID: op.w5bcstyrl2zvei () localhost ! localdomain
[Download RAW message or body]

=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=B5 Mon, 21 Oct 2013 19:37:=
34 +0300, Albert Astals Cid  =

<aacid@kde.org>:

> El Dilluns, 21 d'octubre de 2013, a les 09:12:26, Sebastien Renard va
> escriure:
>> Le dimanche 20 octobre 2013 22:40:25 Albert Astals Cid a =C3=A9crit :=

>> [...]
>>
>> > This is my suggestion:
>> >  * Before KDE SC 4.11.3 all is like now, stable-l10n points to  =

>> KDE/4.11
>> >  and
>> >
>> > trunk-l10n points to master
>> >
>> >  * After KDE SC 4.11.3 and before 4.12 Beta 1 we make stable-l10n  =

>> point to
>> >
>> > KDE/4.12 and trunk-l10n points to master
>> >
>> > This means that for KDE SC 4.11.4 and KDE SC 4.11.5 we will repacka=
ge  =

>> the
>> > same  translations of 4.11.3 (actually we'll package them from
>> > http://websvn.kde.org/branches/KDE/4.11/kde-l10n/ but since that's =
 =

>> outside
>> > the  l10n workflow i don't expect people to touch it much/at all).
>> >
>> > Comments?
>>
>> Hi Albert,
>>
>> Why don't we keep stable branch on 4.11 till its end of life ? Can't =
we
>> package 4.12 translation from trunk ?
>
> We can but it'll be suboptimal for us finding stuff that's broken in  =

> master. I
> guess the question is how much you translators plan to work on existin=
g  =

> 4.11.x
> when 4.12.x is just around the corner.
>
> Cheers,
>   Albert

Hi,

To be honest, it would be safe to freeze 4.11 translations if backportin=
g  =

of KDE PIM and Umbrello patches with new messages to stable is over. ;)

Just my 2 cents.

Best regards,
Yuri
[prev in list] [next in list] [prev in thread] [next in thread]