On Friday 08 September 2006 23:42, David Boddie wrote: > On Friday 08 September 2006 21:11:25 +0200, Simon Edwards wrote: > > On Friday 08 September 2006 01:51, David Boddie wrote: > > > Reading through the SIP files for PyKDE, you find lots of information > > > about the way the KDE APIs have evolved over time. If the bindings were > > > too closely tied to some schedule where development was frozen too early > > > before a release, > > You mean "too late before release" I assume. > Actually, I meant that if the bindings were frozen along with the rest of > the branch then there may not be enough time to stabilize them, especially > if the core developers are working on their APIs right up to the freeze.
I see what you mean. Updates to the bindings in PyKDE won't be able beat the general KDE feature freeze. The dependancies just don't work that way, as you know. PyKDE will have to be an exception to the general rule, and we'll just have to explain this to the KDE release team in advance. They'll understand. :) I still think there is enough time between FF and release to get things updated and tested. Things and features that *don't* depend on the APIs in kdelibs should still obey FF though. > > Or at the very least make a freezing APIs *strongly* recommended. > As long there are no last minute API changes. Sometimes you just can't > recommend something strongly enough. :-/ Last minute API changes shouldn't happen too often. It should be possible to monitor commits to kdelib header files. cheers, -- Simon Edwards | KDE-NL, Guidance tools, Guarddog Firewall [EMAIL PROTECTED] | http://www.simonzone.com/software/ Nijmegen, The Netherlands | "ZooTV? You made the right choice." _______________________________________________ PyKDE mailing list PyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
