[Kde-scm-interest] Git Migration and KTextEditor/KatePart/Kate

[Christoph Cullmann]

On Sunday 04 July 2010 15:23:12 Christoph Cullmann wrote:
> Hi,
> 
> to make developing Kate and its components easier, which atm are:
>  - the ktexteditor interfaces and kate part (which are part of kdelibs)
>  - the kwrite app (part of kdebase)
>  - the kate app (part of kdesdk)
> 
> we moved them to a common repository on gitorious.
> 
> As the conversion kept history, but not tags and co. of old releases, still
> everything is synced back to KDE SVN at the moment.
> (and because for sure, we just want to be released with KDE releases and
> not on our own).
> 
> Would it be possible, after doing the official KDE SVN => Git conversion of
> the main modules, to have the same there and move out the above parts from
> the current modules they are contained to one kate module which is part of
> the normal KDE release cycle?
> 
> That way we could keep the entry barrier for new developers as low as for
> the current gitorious repository (which will then be dropped).
Just to bring that up once more :P Jay, I am a pain.
I have bad conversion rules (bad in respect to tags & branches, otherwise they 
seem to work) or we could use the repository from gitorious for the new 
module.

My question is: would it be acceptable?
The tags/branches for all KDE SC releases from the past would still be there, 
as the main modules would have them, but would having a "kate" module be 
possible while still remaining in KDE SC release cycle (as required for 
ktexteditor and nice for the rest).

Greetings
Christoph