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

List:       kde-i18n-doc
Subject:    Fwd: Re: Post release vs. releasing with 2.0.1
From:       "Thomas Diehl" <thd () kde ! org>
Date:       2000-10-06 6:11:41
[Download RAW message or body]

==================BEGIN FORWARDED MESSAGE==================
>Date: Wed, 04 Oct 2000 19:40:15 +0200
>From: Francois-Xavier Duranceau <duranceau@free.fr>
>To: Thomas Diehl <thd@kde.org>
>Subject: Re: Post release vs. releasing with 2.0.1


Thomas Diehl wrote:
> 
Hi,

I have to say that I disagree with this strategy. Branching the
translations just means that all the work/fixes done between 2.0 and
2.0.1 has to be done twice (in both 2.0.x and HEAD branch). As KDE 2.0.1
is supposed to happen only 3-4 weeks after 2.0 I'd prefer maintaining
the translations in HEAD and start working on 2.1 when 2.0.1 is out.
This avoids duplicate work (and CVS misuse).

Another issue coming to my mind is the "release packages separately"
proposal (by Waldo IIRC). I don't understand how this can work because
ASA a message will change in kdelibs after 2.0 it will break the
translations for kdelibs separate release between 2.0 and 2.1.

FX

> Hi,
> 
> I talked to Matthias Elter about that "post release" we've been
> disussing here for a while already. (For those who don't remember: the
> "post release" was mainly meant for teams that either did not make it
> for 2.0 or would like to improve their already released translations.)
> 
> Originally, it seemed we should freeze the PO files of the respective
> teams on an individual basis. But since we are going to have a complete
> 2.0.1 branch anyway which is supposed to have minimial, mostly security
> related changes it now looks best to branch the complete kde-i18n
> module with it. In effect, every team would have two copies of their
> translations:
> 
> *   one in the HEAD branch (for 2.1, scheduled for Februrary/March next
> year) where the strings will start to change heavily after the 2.0
> release
> 
> *   and one in the 2.0.1 branch (no definite release date yet) where
> there should be relatively few changes since most developers will go
> with HEAD
> 
> This would give all teams the chance to improve translations for 2.0.1
> (or finally to do something for doc translation;-). And it could serve
> as the "post release" for the teams that do not make it for the 2.0
> release. Only problem I see at the moment: that of nobody can tell you
> exactly when the 2.0.1 release is going to happen. Except that it will
> come out "relatively soon" (relative to 2.1, that is).
> 
> Thoughts? Comments?
> 

> Best regards,
> 
> Thomas
> 
> ---
> KDE translation: http://i18n.kde.org/
> Deutsche KDE-Uebersetzung: http://i18n.kde.org/teams/de/

-- 
Francois-Xavier DURANCEAU
mailto:duranceau@free.fr, mailto:duranceau@kde.org
Visitez http://www.kde.org/fr/

KDE -- Color Outside The Lines !



===================END FORWARDED MESSAGE===================


--- 
KDE translation: http://i18n.kde.org/
Deutsche KDE-Uebersetzung: http://i18n.kde.org/teams/de/

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