With this post, I hope to show you that Cervisia is still a valuable developer tool with a bright future. 🙂
Where is the code?
You can find the code in KDE’s subversion repository under branches/cervisia/subversion_support. It is still in a work branch because the cvs plugin isn’t feature complete (compared to the KDE 3.5 version).
Will you make the KDE 3.5 feature freeze deadline?
Realistically speaking, no. As hinted above, the main problem is the cvs plugin. We will not be able to provide all features that the KDE 3.4 version of Cervisia offered to cvs users by August 25th. The KDE 3.5 release definitely comes to early for us.
Does it mean I have to wait for KDE 4?
I hope not. I’m thinking about a separate release of Cervisia with subversion support after KDE 3.5. But I can’t promise it because I don’t have any experiences with such releases.
What subversion commands are implemented?
The current version has support for add, remove, commit, status, annotate/blame and log. After we finished update and diff, the basic features for the daily work are available.
Do you use the subversion library?
At the moment we use a subversion DCOP service which starts the subversion command-line client. The output is later parsed by the svn plugin. We used this approach because of our experiences with cvs but there is also a discussion on Cervisia’s mailing list about kio_svn.
There is a good chance that we will switch to this subversion kioslave in the near future.
How does it look like?
For current Cervisia users, it looks pretty boring. 😉