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

List:       kde-i18n-doc
Subject:    Re: KDevelop translation stuff
From:       Milian Wolff <mail () milianw ! de>
Date:       2014-11-20 16:01:41
Message-ID: 2761920.ogM8bEAgqJ () milian-kdab2
[Download RAW message or body]

On Thursday 20 November 2014 16:18:41 Milian Wolff wrote:
> Hey all,
> 
> besides the issues that Burkhard noticed in our frameworks branch(es), I'd
> like to clarify the current structure of our branches. Could someone please
> verify that scripty is correctly setup? I just went through the important
> repos on projects.kde.org and set the proper i18n branches everywhere.
> 
> kdevplatform, kdev-php, kdev-php-docs:
> 	stable kde4: 1.7
> 	trunk kf5: master
> 
> kdevelop:
> 	stable kde4: 4.7
> 	trunk kf5: master
> 
> kdev-python:
> 	stable kde4: 1.7
> 	trunk kf5: frameworks
> 
> experimental plugins:
> 
> kdev-clang, kdev-qmljs, kdev-qmake, kdev-ruby:
> 	trunk kf5: master
> 
> kdev-css:
> 	trunk kf5: frameworks
> 
> all other i18n branches are set to none. All other kdev-* plugins
> 
> NOTE: I plan to merge kdev-css frameworks into master. I'd welcome it if you
> guys could verify that I can do that. Also we might have done some other
> merges too soon without notifying you guys. Could someone verify that
> scripty follows the above structure?

Note: I just merged kdev-css' frameworks branch into master and updated the 
i18n branch structure on projects.kde.org to:

kdev-css:
	trunk kf5: master

I hope this all works now.

Thanks
-- 
Milian Wolff
mail@milianw.de
http://milianw.de
[prev in list] [next in list] [prev in thread] [next in thread]