To read all comments associated with this story, please click here.
Both Ubuntu and Kubuntu have committed themselves to a 6 month release cycle. Waiting for KDE 3.5 would mean releasing two months late or so.
I'm pretty confident Kubuntu will have KDE 3.5 packages ready, right when KDE 3.5 comes out.
So what's the point in making a "stable" release now and doing a major upgrade two months after that? One sense of the term "stable release" is that the released package set stays the same (except for security updates). The other sense is that the software contained in the release is tried and tested and works without any major bugs. It seems that Kubuntu isn't stable in any sense of the word. :-(
I've previously commented that perhaps Kubuntu should freeze Sid whenever KDE releases and therefore do what Ubuntu does with KDE instead of GNOME. On the one hand, you have a distro that showcases the new KDE releases with the latest and greatest from Sid stabilized into a less bloody repository. On the other hand, development suffers because you can't harness the resources of the Ubuntu project, and you can't accurately predict when KDE will release.
If KDE switches to a time-based release cycle (I think all large community projects should consider this), then Kubuntu should follow this route. Until then, Kubuntu will be essentially a backport of the most recent KDE and associated Kpackages to the current Ubuntu release.
In general, I think comments along the lines of "other than not having the following packages that are supposed to come out in the next 6 months, this is a good release" are very silly. If we keep waiting for everything to come in the next six months, we never release. If you can predict when one large package is due to be released, then you can time your development cycle around that. This is what Ubuntu does with great success. Perhaps the most important design consideration for the Ubuntu project is that it releases shortly after each GNOME release, putting the latest and greatest in the hands of hordes of users. There is no KDE distribution (that I know of) that really focuses on this concept. Does MEPIS release like this?
If KDE switches to a time-based release cycle
AFAIK KDE releases are basically time-based in the sense that there is a minor release every 6 month, but of course it sometimes makes sense to increase that period.
For example releasing 3.5 6 months after 3.4 wouldn't have made much sense as it would have required to freeze development before the annual KDE conference where usually a lot of things are improved.







Member since:
It just would make more sense to me.