Cleanup of plugins and Release Plan

Andreas Pakulat apaku at
Sat Oct 17 14:34:20 UTC 2009

On 17.10.09 06:58:34, Aleix Pol wrote:
> On Sat, Oct 17, 2009 at 6:36 AM, Andreas Pakulat <apaku at> wrote:
> > I've just done a bit of cleanup with our plugins. In particular these
> > have been moved to playground:
> >
> > kdevplatform/veritas - unmaintained and nobody uses it
> > kdevplatform/plugins/git - doesn't work currently and nobody works on it
> > kdevelop/xtest - as with veritas and has usability problems
> > kdevelop/tools/coverage - as with veritas
> I think that's great, it's a good thing we're releasing.
> We talked at some point to have some plugins in extragear, maybe now it
> would be a good moment to think about it. Maybe the git plugin would get
> more attention there attention, I don't know how bad it is anyway...

I've tried it out very recently with the result that it doesn't work at
all in best case and crashes in worst case. If the basic stuff would at
least work, I would've left it in kdevplatform.
> On bugfixing I guess it's hard to get people excited, but we're actually
> being quite stable right now, it's good we're getting freezed soon, that
> will let us concentrate.

Well as I said, for me personally a few months of bugfixing means I can
simply fetch a list of bugzilla and check what from that can be
fixed/how to fix it. While with feature development I have to start from
scratch. And right now I'm not in the mood somehow for the latter...

> String freeze will be more of an issue though, if we need it for bug
> fixing, but we will get there.

We can always try to get an exception. However I don't think this is a
major headache. 
> About 4.1, it would be nice if we could gather at some point for a dev
> meeting, maybe it's too early to think about that, but I guess it's the way
> to get things done in a uniform way.

Even if we don't manage to meet in person an irc-meeting where we meet
up would probably help already. Its simply too cumbersome to define
release goals via mail... Together with a wiki-page where the release
goals are clearly defined (I tried that for 4.0, but maybe there was
simply too much to do for it to work out).


It may or may not be worthwhile, but it still has to be done.

More information about the KDevelop-devel mailing list