As you know, we've been diligently working to port MyEclipse to the latest Eclipse 3.0 milestone build (M6) for a few weeks now. While we had intended to release 3.7 RC2 on all platforms yesterday, when we released 2.7 RC2, we hit an unintended delay.

At Genuitec, we run a multi-step QA process for Enterprise Workbench. In stage 1 QA, our testers pull the latest code from the production build branches and run it within Eclipse's plugin development environment, just as the development team does, in order to speed turnaround of builds and bugs back to development. In stage 1, the 3.7 build passed QA on all platforms.

The next step is to build the full double-click install sets from those same build branches for use by the MyEclipse user community. Once that is done, stage 2 QA is performed using the double-click installers. It was during stage 2 QA that a few problems were found on various platforms. It was sort of a blend of things, but it made the development team uncomfortable releasing 3.7 RC2 until they could dig into the issues. Unfortunately, since the issues are not reproducable in the PDE, it has been rather slow to resolve the problems.

While we truly regret the delay, the development team decided they weren't comfortable with the release and they're really the final authority here on when software is "ready". Management never forces a ship date if development says "no" because we all realize that thousands of people use our products for production use on a daily basis.

We apologize for the delay, understand the frustration it has caused (since we're living it too), and appreciate your continued patience.

--Scott
MyEclipse Support