Re: KDE 4.0.3 packages uploaded (try #1)

2008-03-27 Thread Dirk Mueller
On Thursday 27 March 2008, Dirk Mueller wrote: > Please let me know of any issues you find. the translations are still being generated, I hope I can upload them tomorrow morning. Greetings, Dirk ___ release-team mailing list release-team@kde.org http

KDE 4.0.3 packages uploaded (try #1)

2008-03-27 Thread Dirk Mueller
Hi, KDE 4.0.3 packages are uploaded to the usual place. it might happen that I have to update kdebase-workspace again, but other than that, this should be it. Please let me know of any issues you find. Thanks, Dirk ___ release-team mailing list r

New Features list?

2008-03-27 Thread Andreas Pakulat
Hi, IIRC for KDE 3.5 there was an xml file to accumulate the various changes (specially features) that were done. Does something like that exist for KDE 4.1 too? I mean besides the feature planning page on techbase. Where do I find it if it exists? I'd like to add an entry for the "Print Shortcut

Re: Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)

2008-03-27 Thread Rex Dieter
Kevin Ottens wrote: > Also, per binding we probably a list of "do and don't" which should be > followed by applications using the said binding. > > For instance, the use of the python dbus bindings has shortcomings (as > system-config-printer-applet shown), do we allow apps like that? There's

Re: Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)

2008-03-27 Thread Kevin Ottens
Le Thursday 27 March 2008, Allen Winter a écrit : > I think the Release Team should discuss this and provide a policy > statement. > > Do we allow Python/Ruby/C#/Perl etc. apps in the KDE main modules? > If so, which ones and why? > > Oh, and this is also needed for Jonathan's system-config-printer

Non-C++ Apps in KDE Main Modules (Was: Guidance in KDE Admin)

2008-03-27 Thread Allen Winter
On Wednesday 26 March 2008 16:17:53 Leo Savernik wrote: > Am Mittwoch, 26. März 2008 schrieb Nicolas Ternisien: > > >  >  All modules need porting to KDE4 (and could make nice showcases for > > > the Python >  bindings then). Mountconfig would also need porting to > > > Solid (it already uses > > [