> At this time, build 629 is so far ahead of v2.5.x that I am beginning to > wonder: what will it take to screech this train to a halt briefly and get > release version of v3.0 rolling?
But they list the intended feature list right on their web site: http://www.intellij.com/eap/products/idea/ariadna.jsp I presume until that list is done we won't see a v.3.0. Kirk "David Goldstein" <[EMAIL PROTECTED]> wrote in message news:aeqat9$8sk$[EMAIL PROTECTED]... > I enjoy the feature list, and have built a lot of respect for the JetBrains > guys for their responsiveness to this very busy list. > > At this time, build 629 is so far ahead of v2.5.x that I am beginning to > wonder: what will it take to screech this train to a halt briefly and get > release version of v3.0 rolling? > > You see, as long as we all drive so hard on those have-to-have features, and > the JetBrains folks don't draw that "line in the sand", this sucker will > just keep on rolling, and the bigger it gets the harder it is to test. > > For myself, and I submit to the community here, I would like to see the > focus shift soon (after the JDK1.4 build, 630, stabilizes) to > production-quality tuning: > - memory management > - performance > - winding down the feature-adding machine to GUI tweaks > - prioritized bug fixes > - use an INSTALLER (a-la InstallAnywhere or another top-notch installation > tool) - it will pay off many times over, versus rolling your own or using a > minimum-cost tool. What you're paying for is that critical great first > impression, and for their thousands of hours of getting the cross-platform > and platform-specific issues ironed out (security, saving user-specific > settings, licensing, etc). > > Perhaps the APIs need to follow their own timeline though. > > IMHO the time is nearing to unleash this awesome new rev on the rest of the > Java community. > > It is exactly because the JBs have been so responsive that I worry that they > may feel only pressure to keep adding features, and no pressure to drive > this sucker to a release. It would be selfish and long-term > counter-productive for us as a community to not encourage this shifting of > gears and let these guys continue to earn a living and be rewarded for their > good work! > > ...and by the way, are we going to have to break the bank to pay for > upgrades to 3.0? I'm afraid that my company won't shell out another 200-400 > per user to upgrade just about 1 year later... that would push me back to > 2.6 once my last EAP cycle runs out oh the HORROR! (the Delegate Methods > feature alone has saved me hours of work, and the code folding really helps > my productivity in large classes...) > > Also, I would like to urge the JBs to move soon on the installer if they > still intend to do so and ship anytime in the next 6 months. > Not to assume that anybody isn't well educated, but I just want to warn you > (collective) that the trouble of building a reliable install program is > rarely taked about, but is significant. It often takes many cycles of > correction and wide field testing to really get it right; especially when > it's cross-platform! > > Thanks and best regards, > DaveG > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
