Thanks to the massive work of sysadmin and others (like Ian Monroe), kdelibs and kdebase are now converted to Git.
In parallel, the move of all kate related code to the kate.git was done and announced. Kate Part / App + KWrite reside now in kate.git on git.kde.org and this is the central place for kate development, like it was already before, but now without the shadow-copies in three other repositories.
As it has shown in the past, this centralisation of parts which belong together helps to get stuff done for our project. The Get It! page on kate-editor.org is already updated (as now documentation is in the module, too, and some CMake parameters have changed).
I can only say: If you want to add some feature or hassle with some bug, give it a try. It’s dead easy to get and compile a fresh Kate (even with a bit older kdelibs around). You are welcome
P.S. Thanks again all the people working on the transition to Git and sysadmin for operating the nice projects.kde.org and git.kde.org services!
As Dominik already points out in his blog, Kate has made nice progress for KDE 4.6.
Some of the latest fixes, like for some nasty search bug didn’t make it in RC1, btw., I was too lame with Git -> SVN syncs.
Anyway, I have now synced and backported to KDE 4.6 branch all pending fixes.
For the next KDE SC release 4.7 (here you go, I wrote SC :)), I hope this syncing will no longer be necessary.
At least Kate app + part + KWrite should then be only in the kate.git.
I can live with ktexteditor remaining in kdelibs, if removing that and still keeping BC and SC would be too much work. But part and app are at most runtime dependencies anyway.
Last but not least, I wish you all a good start into a happy new year
Goodbye to Gitorious, welcome to git.kde.org.
You can find the Kate project here.
The “Get It!” page on the homepage is updated, too.
Push access is still restricted, but that will not last for ever
Thanks to the sysadmin team of KDE, thanks guys, for all the work you put into the new infrastructure (and to help me with my faults
And thanks to Gitorious, it was a nice time there, and I learned to appreciate Git, like many Kate developers (some appreciated it even before).
Like before, all changes in SVN and Git will be synced by me, as Kate is still released with KDE SC from SVN.
For the future I would like (and most kate devs, too) to develop solely in the Kate repository and have Kate released from there with KDE SC (instead spread over several modules).
But this must still be discussed with the release team after 4.6.
Beside, this means no split off from KDE, but it makes contributing to Kate that much easier, given atm you would need to checkout/clone kdelibs + kdebase + kdesdk and try to build there the Kate relevant parts, which is just no fun, if you just want to hack on some small bug or feature :/
We tried to move weeks ago already, but in our current repository some small glitches occured during the SVN => Git transition.
I have redone the conversion now and soon we will be on git.kde.org (if I not screw that again, thanks already to sysadmin for all help, now and in past!).
Still some small stuff will then need to be ported, which I will do after the initial repository is up there.
After this, the repository on Gitorious will vanish.
I will keep syncing KDE SVN and the repository, until KDE has migrated, too.
But please, if you work on features rather than simple oneliner fixes, use the git repository on git.kde.org after it is announced to be available.
You have automagically a git account and it makes merges for me much easier, if there are not too many conflicts from SVN -><- Git.
I hope the Kate team can keep the kate repository then as sole workspace, as working on the kate part/app is much easier for all contributors if you don’t have to get whole kdelibs/kdesdk. But that is still not discussed out I think, release team has a say here, as I would rather like to stay in KDE release cycle.