faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: wow
by Anon Reloaded on Wednesday 30/Apr/2008, @22:20
|
"I think you're dead wrong. Openly praising bad ideas isn't helpful in the least."
Agreed.
"Everyone has said, "wait for KDE 4.1, and then you'll have the stable desktop with the common features people are looking for."
Then they've spoken out of turn, or are being very optimistic. You don't bring a huge departure like 4.0.0 into something near-perfect in just 6 months.
"Refactoring plasma at the last minute as well does not bode well for stability either"
"3 months before scheduled release" or "one month before feature freeze" or "just after half way through the dev cycle" (take your pick) != "at the last minute". Get some perspective, please.
"If 4.1 isn't stable, it will only feed the cynics and haters more."
Cynics and haters don't need feeding - if 4.1 rules everything in the world, they will continue to hate. And anyway, so what?
"I think the real solution here is to move to something like git, where plasma breakage can happen in a seperate repository. Refactor it there, and then test some builds with it."
Agreed - I'd like to see more and more devs using Git. It seems to be an excellent way of easily managing branches.
"If it works, then include it in 4.1"
Disagree - there's no point having another 6 months of third parties writing against outdated APIs. The new API should be in 4.1, full-stop. And it seems it does work, anyway, so the point is moot.
"but what is happening now, is that people are breaking plasma in SVN, and talking about changing things up even more."
Major changes happen in trunk three months before release! - sky is falling, etc. This is basically what is supposed to happen. Frankly, I'd be worried about the future of KDE if it weren't. |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
