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

List:       kde-i18n-doc
Subject:    Re: KDE_3_0_BRANCH and i18n strings
From:       Stephan Kulow <coolo () kde ! org>
Date:       2002-03-26 13:01:28
[Download RAW message or body]

On Tuesday 26 March 2002 13:42, Thomas Diehl wrote:
> Am Dienstag, 26. März 2002 12:59 schrieb Stephan Kulow:
> > > as you might have read in the previos posting, kde-i18n is not branched
> > > yet, mainly because it wasn't decided yet which of the branches (HEAD
> > > vs KDE_3_0_BRANCH or even both) will be message-merged into kde-i18n.
> > >
> > > I can branch KDE_3_0_BRANCH as soon as the tag-moving finished (takes
> > > ages in kde-i18n). But I assume there will be a lot of time between
> > > 3.0.1 and 3.1 release, so it might be just convenient to not branch
> > > kde-i18n at all, and msgmerge KDE_3_0_BRANCH into HEAD kde-i18n. This
> > > way you can continue on improving the translations for 3.0.1/3.0.2. I
> > > assume it doesn't make sense to work on the HEAD branch for now (as
> > > major amount of i18n string changes are possible).
> >
> > I would prefer branching now instead of after 3.0.1. From past
> > experiences I think I learned, that leaving the developers alone for too
> > long i18n-wise tends to be more work in the afterrun :)
>
> I also think, the tagging / merging policy we had in the last releases were
> pretty good. There are always people who would like to keep HEAD
> translations up-to-date (for what reasons ever), while others stay with the
> branches until they are had their last official release.
>
As maintainer of the xx language, I vote for the branch too, or to say so: xx 
xx :)

Greetings, Stephan

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