[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-25 12:46:17
Message-ID: 2570949.YGWKCqtWI9 () milian-kdab2
[Download RAW message or body]

On Thursday 20 November 2014 23:20:12 Luigi Toscano wrote:
> Milian Wolff ha scritto:
> > 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.
> 
> Crossing finger, all moved. Let's see after next scripty run tomorrow.
> Quick note: kdev-python/master is not tracked anymore, as it's the same as
> 1.7 and nothing will be released from there before frameworks is merged
> into it.

Thanks again Luigi!

I just read this in my IRC backlog:

[20:58] <blueck> milian: scripty reports kdevsnippet.pot as obsolete template 
in trunk/kf5, but catalog is still used in stable. Was kdevsnippet removed ?

Indeed, in master/kf5, the kdevsnippet plugin is dead and was removed. Sorry, 
we were not aware that we must notify you about such things. We'll try to do 
so in the future.

In stable, the plugin is still there.

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