From kde-pim Thu Apr 07 14:18:17 2011 From: Kevin Ottens Date: Thu, 07 Apr 2011 14:18:17 +0000 To: kde-pim Subject: [Kde-pim] Re: kdepim-4.6 ? Message-Id: <201104071618.23406.ervin () kde ! org> X-MARC-Message: https://marc.info/?l=kde-pim&m=130218599021652 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0573865959==" --===============0573865959== Content-Type: multipart/signed; boundary="nextPart1816399.v3cIC0BL65"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1816399.v3cIC0BL65 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Thursday 7 April 2011 15:58:22 laurent Montel wrote: > We have a real problem with kdepim-akonadi I think, we don't have release > plan for it and it's not normal. Thanks Laurent for bringing that up, it's pretty much needed IMO. =20 > We wanted to release it with KDE-4.5 we didn't release it and we decided = to > release with KDE-4.6 and not released. > After that we decided to release with KDE-4.6.2 so yesterday but it was n= ot > released... >=20 > So I think it's time to decide if we want to release it or not and when. I think you summarize the issue pretty well there... I think there's a lack= of=20 will to release at that point, and that probably comes from a lot of fear i= n=20 our own product (likely a combination of "aftermath of KDE 4.0", how painfu= l=20 the port has been and how critical kmail is). > As I understand there is a meta blocker bug: > https://bugs.kde.org/show_bug.cgi?id=3D270261 > I read this two bugs... and for me it's not blockers. >=20 > There is perhaps some problems on kmail but kdepim is not just kmail > there is kadressbook, kalarm, ktimetracker which were improved in 4.5-4.6 > but for the moment we can just use version from 4.4 and it's not good for > developers I think. > How we can motive new kdepim dev to fix some bugs in kdepim-trunk if they > are not sure that we will release it a day ? Exactly, I'm in the same boat there. I lost most of my interest in the PIM= =20 stack after the latest Akonadi meeting I attended, we were very close to go= =20 ahead with a release and never did, again based on fear. Of course, at the= =20 time the migration still had strong issues, and I admit that could indeed b= e=20 considered a showstopper. But now... Most people I know who started to migr= ate=20 are actually able to use the thing, and it didn't burn their house, didn't= =20 kill their pets and most importantly didn't loose data. I even know people using master daily... Yes, kmail isn't perfect, its 4.4= =20 version isn't exactly a walk in the park either. korganizer seems in better= =20 shape than its 4.4 and so on... Can we stop the trend based on fear and release ASAP now? It's chicken/egg= =20 situation now, not releasing ensure not enough stabilization work happens, = and=20 ensures lack of developer retention. I'm afraid that waiting for much longe= r=20 doesn't make sense anymore. > Perhaps we can release just kdepim-runtime-4.6 so developpers will able to > use akonadi resource, and not wait that we release perhaps a day > kdepim-4.6... That one is even more critical than the rest of kdepim indeed... Right now= =20 it's basically impossible to start any meaningful akonadi based application= to=20 put in the hand of our users (like my current pet project) because said use= rs=20 are still having the kdepim runtime of 4.4... so the most interesting=20 resources are crippled, seriously limiting the feature set we can offer. =20 > So I think that now it's really necessary to define a plan or decide to > kill kdepim-akonadi. I wouldn't kill it... But not defining a firm plan (not something we give u= p=20 on two weeks before release) indeed gives it a gloomy fate. So yes, we need= an=20 aggressive plan there. We won't release a perfect product, it'll have bugs= =20 (bugfix releases are there though), but it doesn't loose data! =20 > If we don't define it nobody will work to fix bugs and release it. > and I think that for kde-4.7 we will decide to wait until kde-4.8. That's what gets me worried indeed, we got a trend there. Could we get back on the KDE release train please? =20 Regards. =2D-=20 K=E9vin Ottens, http://ervin.ipsquad.net KDAB - proud patron of KDE, http://www.kdab.com --nextPart1816399.v3cIC0BL65 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk2dx68ACgkQB0u7y43syeLmjACgmT2qChD0QILjhNtCY0kNfpWd K1kAnibpNohx9hZ2XehWF+xSCXgVH39s =dj+s -----END PGP SIGNATURE----- --nextPart1816399.v3cIC0BL65-- --===============0573865959== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE PIM mailing list kde-pim@kde.org https://mail.kde.org/mailman/listinfo/kde-pim KDE PIM home page at http://pim.kde.org/ --===============0573865959==--