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

List:       kde-i18n-doc
Subject:    Re: extragear-network
From:       Rinse de Vries <rinsedevries () kde ! nl>
Date:       2006-08-07 21:23:40
Message-ID: 200608072323.41220.rinsedevries () kde ! nl
[Download RAW message or body]

Op maandag 7 augustus 2006 22:07, schreef Rafael Rodríguez:
> Yes, but I expected extragear apps, having a development cycle separated
> from KDE, being all in trunk. I didn't know they could use branches inside
> official svn also... Because their branches needn't be the same as KDE
> ones.

l10n is outside of the KDE module, AFAIK because of that.
l10n is split up in two branches, stable and trunk. Project can use both or 
just one of them, its completely up to them, there is not a guideline that 
they follow. 
>
> For example, in extragear-network it's ktorrent in branches and in trunk.
> Is there a ktorrent 3.5 version and a 3.4 version and so on? I'm not sure
> of it...

ktorrent is a good example of how stable and trunk should work: ktorrent is 
developed in trunk, and as soon as they come close to a release, the copy 
their work into stable. New development continues in trunk, while translation 
teams can start/finish their translation of ktorrent in stable, without 
getting new/fuzzy strings all the times.

Another example is Amarok: Amarok is developed in trunk; the version in stable 
is de previous one. As soon as Amarok starts working on version 2.0, the 1.x 
version will be moved to stable and maintained over there, and 2.0 continues 
in trunk (bit like kde does with 3.5.x vs 4.0)

Regards, Rinse

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