[Kde-pim] progress

Ryan Novosielski novosirj at umdnj.edu
Fri Oct 12 15:04:46 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason 'vanRijn' Kasper wrote:
> So, if I may be so bold, I'd like to portray a little bit better image of
> the hard work we've done in KPilot over the last 8+ months than "probably
> won't be ready".  =:)  As I explained in the e-mail I just sent, we actually
> do have a pretty good story to tell, and "probably won't be ready" sounds
> like KPilot won't be at all functional in KDE4.  It actually is, but we
> don't have enough manpower to bring all of the functionality from KDE3
> forward just yet.  So.... maybe something like this?
> 
> KPilot's hard-working team of 2.5 have been spending their time getting as
> much done in preparation for KDE4 as possible.  KPilot's lib, daemon, main
> UI, and configuration screens have been ported and are operational.  Due to
> a very aggressive Summer of Code project and lots of Real Life (TM) thrown
> in, not all of the old conduits have been ported yet, which means that
> calendar, todo, and address syncing won't be functional until KDE's
> 4.1release.  The good news is that
> 3.5.8's KPilot is the most stable release to date.  The focus in KPilot for
> KDE4 has been to clean up as much cruft as possible, to establish a solid
> foundation that all of the conduits will now share, and to create a new
> conduit in place to exercise that base code (namely, Bertjan's new keyring
> conduit).

OK, but here's my problem -- what happens when/if I upgrade to KDE 4.0?
Do I not get KPilot? Do I get a KPilot that is there and will execute
but "not all old conduits" function (why would anyone run KPilot if not
for calendar, todo, and address? isn't that the entire point of the
application)?

I'm not trying to bust chops here, but people use this for productivity.
A broken release is almost worse than no release at all. The best case,
it sounds like (and maybe this is exactly what you're doing, but it's
not stated here) is to release KDE 3.5.8 with KDE4, but what you had
written indicates that all of the KDE3 code was removed. Perhaps this is
from a different branch?

Excuse me if I'm asking ignorant questions. :)

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHD37+mb+gadEcsb4RAurlAKCJSL70MbaRllU2CUyvMp7ECNEE0wCgogoY
RCkAu/JWAr047YNeaHV2rwQ=
=fTMr
-----END PGP SIGNATURE-----
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/



More information about the kde-pim mailing list