Andreas Pakulat apaku at gmx.de
Fri Oct 17 15:17:01 CEST 2008


Unfortunately we (the KDevelop team) are still lacking behind on our
important features, which means we won't make the cut to release KDevelop
4.0/KDevplatform 1.0 with KDE 4.2. 

Nonetheless we're making enough progress to be able to release a first beta
with KDE 4.2.

The question is wether including the two modules with the rest during the
KDE 4.2 release cycle would be ok, or wether this would produce too much

To make that clear: KDevelop would be version 3.9.81 on next monday,
KDevplatform 0.9.81. And so on until the tagging of KDE 4.2.0 where I'd
switch to x.9.91 for our first beta release.

The alternative I currently see would be that we'd do the release of
tarballs for another 2 alpha's and the betas afterwards ourselves. I'd like
to avoid that, unless of course you think the above plan causes too much
confusion (stable KDE 4 release with a beta of one app/lib).


After your lover has gone you will still have PEANUT BUTTER!

More information about the release-team mailing list