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

List:       kde-i18n-doc
Subject:    Re: Time to split translations for KF5?
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-04-01 7:23:02
Message-ID: 2278157.SVkIa1NHCB () xps
[Download RAW message or body]

El Dimarts, 1 d'abril de 2014, a les 08:48:02, Burkhard Lück va escriure:
> Am Donnerstag, 13. März 2014, 22:48:19 schrieb Luigi Toscano:
> > Hi all,
> > 
> > as you have probably noticed, right now the status of our translation
> > branches is quite complicated.
> > 
> > Few modules in _trunk_ tracks Frameworks 5-based code: for example all
> > frameworks/ and kde-workspaces/. The number will grow: in the next weeks
> > kde-workspace and kde-runtime will be split, creating additional
> > translations modules or files.
> > 
> > If the keeps the things this way I suspect that we will have some
> > troubles;
> > when KF5-based applications will be released  (kate, okteta, konsole are
> > almost ready) we will need to track:
> > - stable 4.x branch (4.13?)
> > - devel 4.x branch (4.14?)
> > - KF5-based applications (5.x).
> > so 3 branches!
> > 
> > The same for the documentation; and please consider that few modules are
> > not tracked (the documentation of frameworks module for example). Another
> > change: KF5 documentation has been ported to use DocBookXML 4.5, so you
> > need to compile few Frameworks modules to generate translated
> > documentation. I can help with that for now, but this enviroment will be
> > more and more needed. But this is another issue.
> > 
> > So: as most of you remember we had a trunk/l10n-kde3 base directory for
> > KDE3-based translations. Is it time to create trunk/l10n-kf5 directory and
> > track KF5-based modules there?
> 
> I think yes, we apparently need:
> 
> 1) stable/l10n-kde4
> modules kde* 4.13/4.14 except kde-workspace 4.11 + all stable extragear at
> least until the end of this year
> 
> 2) trunk/l10n-kde4
> modules kde* master but without kde-workspace, which does not have a
> "master" branch + extragear + playground
> 
> 3) trunk/10n-kf5
> let's start with frameworks(master), kde-workspace(master), plasma-
> framework(master)(?) and kde-runtime(frameworks) when this module has been
> splitted (will happen soon)
> Each module/application, where development switches to a frameworks based
> branch (kate, konsole, okteta) should be added here consecutively.

Is there any reason we can't have 2 and 3 together? I don't see any other than 
the name being l10n-kde4 but if it was l10n-master or l10n-unstable I would 
not see any problem.

Cheers,
  Albert
[prev in list] [next in list] [prev in thread] [next in thread]