Add new comment

Yesterday we began talks on our KMM4 mailing list to start listing the blocking issues we have for a beta release. I've been using the SVN version for the last 2 months, and it has its fair share of errors, but most are being solved pretty quickly, thanks to the big effort of our development team. So, are we in shape for a beta?

Having taken 9 years for a 1.0 release, you can tell we don't take releases lightly. We are now listing the blocking issues, and from there we will check whether we are in good shape or not. So far, I only had 3 major issues. 1 is fixed, the other one is a usability problem, but not a blocking bug, and the third one is a minor nag, but in the ledgers, so I would like to see that resolved before beta.

Then, we have a plugin still pending to be ported. The aqbanking plugin has not been ported yet. The KDE3 one is in AqBanking's repository and it works with an old version of AqBanking. We are going to work on porting it to KDE4 and to use the new version. That will open the door to new features in AqBanking, and we are bringing the code of the plugin back into KMM's repository in the process. We'll see how that goes, but I think it will work out ok. Also, while talking to Cristian about it, I realised that other apps could benefit from this kind of plugins. If they implement a plugin interface similar to ours, we could have a common set of plugins. Libofx and AqBanking come to mind now, but also Akonadi and others could be implemented as plugins, and having something like the kipi-plugins could save us all some work. Who knows?

So, perhaps we are only one big push away from a beta release. I hope no other big issues arise from the discussion in the mailing list.