KDevelop 3.4 translations.

Stephan Kulow coolo at kde.org
Wed Feb 21 09:46:17 UTC 2007

Am Mittwoch, 21. Februar 2007 10:38 schrieb Amilcar do Carmo Lucas:
> Merging the kdevelop/3.4 branch into KDE/3.5 branch will bring us some
> problems:
> - Confuse the users that do use svn checkouts
How does it confuse them? Because they out of the sudden get the maintained 
version and no longer the "who cares" version? Yeah, I can see their problem 
with that.

> - Make me change tons 15+ website files (I still have no clue how to change
> the top table of the branches_compiling.html page in a nice way)
> - Confuse our website translators
Oh boy, how many of them do you have? 20? How many users are confused because 
you need kde-i18n of KDE 3.5.7 for kdevelop 3.4?
> To avoid that all we need to do is to change two files in KDE source tree,
> branches/stable/l10n/scripts/get_paths
>   has the translation path of the stable releases,
> branches/KDE/3.5/kde-common/release/versions
>   has the source path of the stable releases.
> This has the advantage of preserving history and requiring the less amount
> of changes/confusion.
> And NO, that distro packagers will not be confused by this, they just grab
> the tar.bz2 files that we provide them, they do not use SVN.
> If they do that (use SVN), then why the hell do you provide tar.bz2 files ?
They do use the tars, but they often grab bug fixes from the 3.5 branch.
At least remove the kdevelop in that branch and replace it with a directory 
that only brings a README

Greetings, Stephan

More information about the KDevelop-devel mailing list