stab at KDE 4.0 release?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

stab at KDE 4.0 release?
by John on Wednesday 02/Apr/2008, @09:18

> I would not provide a "stable" release full of bugs.

looks like some KDE devs didn't like the 4.0 release full of bugs either :)

Related Links

·   Articles on Applications
·   Also by John
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: stab at KDE 4.0 release?
by Caulier Gilles on Wednesday 02/Apr/2008, @11:57

Absolutely (:=)))

Gilles Caulier

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Aaron Seigo on Thursday 03/Apr/2008, @09:09

the irony is that a little further below you complain (rightfully) about how it wasn't possible to develop against the always moving libs from last summer (pre-4.0). 4.0 specifically, purposefully addressed that issue by getting the core functionality moved to "stabilize! complete features!" rather than "more new developments!". the expectation was that this would allow application developers such as yourself to get your efforts on track instead of being continuously held up by a never ending library development party.

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Anon on Wednesday 02/Apr/2008, @14:18

4.0 is not a stable release. It is a development release. 4.1 will be the first stable release.

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Gilles Caulier on Wednesday 02/Apr/2008, @14:55

And what about printing interface ???

In digiKam for KDE4 i have disable all KDEPrint support because all api become obsolete/unmaintened (fix me i'm wrong)

KDE 4.1 will re-enable it or find alternative (using QT 4.4 for ex.)

Can you said than KDE 4.1 will be the first release ready to use in production if printing interface cannot be used ?

Gilles Caulier

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Aaron Seigo on Thursday 03/Apr/2008, @08:54

printing already works in trunk/, so there's no need to wonder idly anymore. it uses the printing support from Qt 4.4 and it's progressing rather nicely.

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Gilles Caulier on Thursday 03/Apr/2008, @09:38

Thanks for the info Aaron. I wil review digiKam printing code in this case.

Gilles Caulier

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Erunno on Wednesday 02/Apr/2008, @15:09

Well, then why is KDE filed under the "Stable" section on kde.org? And why does the release annoucement for 4.0 not contain any warning about this being a relase targeted mainly at developers? Not that I intend to beat a dead horse but I'm also somewhat allergic to revisionism. And I don't count developer ramblings on obscure blogs and mailings lists. kde.org being the main internet portal for KDE is as official as it gets. And it states that 4.0 was stable although reality disagreed on a regular basis.

Anyway, 4.1 looks like it's going to be a solid release and with 4.2 most applications should be finally ported.

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Gilles Caulier on Wednesday 02/Apr/2008, @23:32

When i have started to port digiKam to KDE4 at July 2007, i have seen imediately several problem in core libraries. I don't speak about full desktop which for me have been unsuitable at the date.

This duing a lots of major changes in API. For big a big library as KDE, the list of regression tests is simply huge...

This is why is have never planed to try to plan digiKam 0.10.0 for the first KDE 4.0 release. It been impossible to have a stable appplication.

You have right. KDE 4.1 will be better, and certainly KDE 4.2 the first release which can be used in production.

This is not a critic. It's just the reallity. And if you look into the pass, the same situation have been seen with KDE 2.x to KDE 3.x transition.

Gilles Caulier

[ Reply To This | View ]

Re: stab at KDE 4.0 release?
by Aaron Seigo on Thursday 03/Apr/2008, @09:01

> For big a big library as KDE, the list of regression tests is simply huge...

thankfully the number of real regressions has been rather small. there are some important ones, mostly that we knew about already due to technical issues we ran into (the ssl and proxy issues are good examples o those).

> It been impossible to have a stable appplication.

it may have impossible for digikam, i can see that, but dozens of apps shipped for 4.0 and were quite stable.

that said, you're quite right about "chasing a moving API" being a major blocker for application developers. getting 4.0 out the door was a vitally important step for addressing that and increasing the stability / lowering the regression counts in the core libs. this happens best when drastic new changes aren't happening any more, more applications stress it and more users do different things with it. it's far more pleasant and realistic to develop apps against the kde4 libs at this point.

as such, i think we'll see a bloom of applications in the 4.1-4.2 timeframe, digikam being a good example of that with it's release date of september.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"KDE: Get Over It!" -- Ivan E. Moore II
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.