[Kde-extra-gear] Re: Branches and translations

Joris Guisson joris.guisson at gmail.com
Tue Jun 28 15:41:21 CEST 2005


I'm confused here, why are stable tags and branches needed ? Seeing
that there isn't going to be a kde-extra-gear package.

If people want to get a stable release from your app, they can go to
tags/appname/ and checkout the directory with the latest version number.

On 6/28/05, Sebastian Trueg <sebastian at trueg.de> wrote:
> 
> >> Would somebody with sufficient karma please create :
> >> branches/ktorrent/
> >> branches/stable/extragear/network/
> >
> > You mean tags/stable, right ?
> > This is already created and stable means a point to the latest stable
> > code. You need write to sysadmin at kde.org to handles creation
> > permissions
> 
> ok, one last time (because I tried to bring this up many times but no one
> was interested):branches/stable is there and scripty is working on it. So
> simply put
> ktorrent into branches/stable/extragear/network, add the network dir to
> branches/stable/l10n/scripts/xxx (not sure which script, it's the one that
> converts extragear/network to extragear-network or the other way around to
> find the original strings, ask coolo or wait two days until I am home) and
> copy your stable translations to the stable l10n branch (I created a brute
> force script. If you are interested, let me know).
> IMHO there is no sense in creating a stable tag for extragear packages as
> they will never be packaged all together and it would mean that you had to
> move around tags everytime you create a bugfix release. I don't want to
> waste my time on that. With a stable branch which can also be translated
> (you could even introduce new messages!) and the trunk maintaining the app
> should be easy and comfortable.
> Cheers,
> Sebastian
> 
> 
> 
>


More information about the Kde-extra-gear mailing list