- This topic has 4 replies, 4 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Well, as disappointing as not having the newest version out yesterday was, I’d prefer to have you guys do it correctly rather than get all excited about the release and then fight with it because of some problem and have to get a fix 2 days later.
I hate when companies release a product just because its “ship day” even if the software isn’t ready just because they can release a patch later.
Thanks for understanding. The dev team is making good progress and at this point the issue seems to be a bug in the new M6 plugin loading scheme. We’re currently testing a workaround that appears hopeful. Fingers crossed. 🙂
–Scott
MyEclipse SupportScott,
Is the the large gap between 2.7 and 3.7 just an aberration.. or is 2.x the tier 1 platform and 3.x always lags in terms of priority and resources? It appeared they were always in synch.. and that’s why I went with 3.x since its on the next major release of eclipse. I’m pretty disappointed living with some serious bugs in 3.6 and I’d like to avoid that happening again. What do you recommend?Thanks,
MarkMark,
We’ve *always* recommended that everyone use Eclipse 2.1.x for all production work due to the instability issues in the 3.0 milestone builds. Eclipse 3.0 is SIX MONTHS from going final and is in constant flux while the team works on some very big changes. It’s just not going to be as reliable as the 2.1 versions.
As far as resources go, we always deliver the 2.1.x stream internally first since that is the current production build. We then focus on the 3.0 port. Prior to M5, this wasn’t a big deal, but M5 broke backward compatiblity in a big way and we now have a branched codebase to contend with. There were literally hundreds of changes needed to create the 3.7 builds and it just took a lot of time. In fact, more than we anticipated. Testing is going well, but we’ve already identified a bug in Eclipse’s new plugin loading architecture and noticed a background thread problem too.
In short, if you want stability and more rapid releases, stick with 2.1.x. If you want to experiment with the latest features and don’t mind “bleeding” a little while you play on the bleeding edge, go with 3.0.
–Scott
MyEclipse Support@pholister wrote:
Is the the large gap between 2.7 and 3.7 just an aberration..
The jump from Eclipse M4 to M5 involved an extensive set of incompatible API changes. (Basically the main reason why the new Eclipse is 3.0 instead of 2.2) and 95%+ of existing plugins have to be retooled. Considering the scope of myeclipse, it seems fair to say that this (2.7 to 3.7) will be the largest individual gap between stable and ‘testing’ releases. That said, the testing version will probably start lagging a little longer behind the stable version than it has been because the code is increasingly different.
