--===============1200015668== Content-Type: multipart/signed; boundary="nextPart2418310.T6ye4Y35Hb"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2418310.T6ye4Y35Hb Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, On Friday 10 December 2010 11:54:45 Will Stephenson wrote: > On 10/12/10 11:27, Andras Mantia wrote: > > Having an extension for the beta time by itself will not help. If nobody > > fixes bugs, they won't go away. If developers cannot find time to work = on > > kdepim, that's fine, but in this case we should consider of not releasi= ng > > kdepim together with 4.6.0. I wish we could, but releasing in its curre= nt > > state will do more harm than good, as there are obvious shortcomings bo= th > > in migration (very important!) and daily usage. I agree with Andras here as well, having another beta won't gain us much. I'll stay out of the discussion whether or not to release KDEPIM with KDE 4= =2E6=20 or not, as I don't know the current state well enough for that. KDEPIM definitely would benefit from more developers, as otherwise bugs ind= eed=20 won't get fixed. Thankfully, there are some developers like Tobias, Laurent= =20 and Andras actually using KMail2 and therefore contributing some bugfixes,= =20 which is great. However, IMHO there needs to be a bigger developer base for= =20 having a healthy project. > Agreed. And I don't know how it will improve because there is no > communication from whoever is managing the kmail2 work in KDE PIM or at > KDAB. There is no communication because nobody really is managing the work. The=20 developers doing KMail2 bugfixes right now do it to fix their own problems,= =20 there is no "managing" involved. And KDAB is working on the mobile version,= so=20 don't expect any desktop work coming from there. Of course, the shared bits= =20 like Akonadi benefit from the mobile work a lot. So since there the work on the desktop version is not much, there is also n= ot=20 much communication. > Could someone who is qualified to speak for one of the above give a > statement on where we stand and where we are going for 4.6 so that my > imagination doesn't run wild? Regards, Thomas --nextPart2418310.T6ye4Y35Hb Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAk0CRA8ACgkQKglv3sO8a1OloQCeNL15rEsl8/JTn0eLzYZjKccz TyMAnjna7W2XH+NdkHA8yPMwOzhKd/fY =v3/X -----END PGP SIGNATURE----- --nextPart2418310.T6ye4Y35Hb-- --===============1200015668== 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/ --===============1200015668==--