"Oh, shit! There is no plan, stick it where it will fit even if it quadruples the number of clicks required to get it done, go ahead... move it from where it was designed to go just to get it working, if we don't get something working out quick, then the cat's out of the bag and the users will figure out that we haven't really haven't had a plan since some idiot release 4.04 as a final release when it was really pre-alpha in June 2008 and we have been robbing Peter to pay Paul to get a justified 4.1 out the door ever since, but we bought some time by changing the release numbers so quickly the community really thought it was getting something other than the beta releases leading up to where we are today. They won't all stay in the dark forever, so hurry damnit! We are understaffed, over loaded, and have an enterprise size code-base to bring together on duct-tape and bailing wire resources.
Hmmm that sounds EXACTLY like the usual software development cycle in just about every company I've worked in, in the past 15 years... and in almost all instances we were developing high end commercial software that was going into equipment worth 10's of millions of dollars/euros. :-P In other words... KDE development isn't a lot different than commercial software development cycles. That said, KDE4.4.0 is working quite nicely for me so far. No real serious complaints outside of the known regressions/bugs that are already reported (so far). :-) C -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org