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.
The website is now on a new server, which is a lot faster than the old one and software/hardware is fresh again.
Hope the problems we had in the past few weeks are over now.
No other real downtimes are planned, perhaps some reboots but nothing more than some minutes 😉
Hope I can now finally setup my planned automated unit-tests and build 😉
The DNS transfer seems to be faster than thought, still some people might arrive at the old server, where now only a stupid “Maintainance” page is up. The IP of the new server is 184.108.40.206.
In the last weeks, the homepage was sometimes down, as the server it is on is slowly dying. I just negotiate the transfer to a new one. That one will allow additional stuff to be run, guess we than even have nightly unit test runs (at least I hope so) 😉
Therefor it may be, that the site is not reachable, as DNS transfer might always take some days.