on Sep 20th, 2011Eclipse Juno Milestone 2, available for download
With summer behind us and autumn almost here (in the northern hemisphere), you can feel the change in the air.
The Eclipse and Equinox teams have made Juno Milestone 2 available, however, these milestones are no longer based on the Eclipse 3.x stream. Starting with this milestone, we will be encouraging users to actively test the 4.2 stream. The Eclipse Juno release (coming June 2012) will be based on the 4.x stream.
There are a few goodies in this release including Quick-Fixes for loop refactoring:
An enhanced Ant editor:
And some fancy new transitions:
Checkout the entire New and Noteworthy. Or better yet, download the milestone and take it for a spin.
Related posts:
- Eclipse Juno Milestone 5, available for download
- Eclipse Juno Milestone 1, available for download
- Eclipse Juno Milestone 3, available for download
- Eclipse Juno Milestone 4, available for download
- Eclipse Juno M5 and Indigo SR2 RC2
While I appreciate the hard work on 4.x stream, looking at the current (unusable) UI state I wonder how one can seriously make a decision to run the *stable* Eclipse release based on the current 4.x UI code. At least on Linux the new 4.x UI can’t be used without major issues like disappearing view toolbars, not working perspectives etc. Yes, I didn’t entered bugs for it, because one must be blind to overlook such major regressions.
This reminds me the p2 integration into the 3.4 release, where we needed 3 releases after it to make p2 finally working. Yes, this will increase the test coverage and also the rate of incoming bugs, but I doubt that this will increase user acceptance or help to solve existing issues.
May be I’m alone here, but I think that better way to increase the test coverage is… to write tests (surprise surprise…), not to promote end users to beta testers.
My only hope that 3.8 will be still tested and maintained while spending so much time on fancy 4.x stuff…
Sorry for such negative reply, it is just a voice of a frustrated user. One good thing this time (comparing with p2 integration into 3.4 M7) is that the pain starts earlier, so that hopefully more issues will be fixed before code freeze.
Regards,
Andrey
Andrey,
I’m not on the planning or architecture councils (or on the Eclipse PMC for that matter) so I can’t speak for them. But I do think that the approach they are taking with the 4.x stream is a good one. There are really 3 different ways they could operate:
1. Do everything internal at some company and release it when it’s ready.
2. Do everything in the open, but slowly and only release when everything is perfect.
3. Do things in the open and release early / release often.
I think we can both agree that #1 is a non-stater. Just imagine the negative / close source responses they would get if they did this. As for #2 vs. #3 this is a hard line to walk. You certainly can’t get manager approval for very long if you don’t have users. And if you don’t release and push people to use it, you’re not going to get users. Yes I would love someone to go off and build me the perfect IDE, without bugs, for free, but is this really realistic?
I think the approach they’ve taking with the 4.x stream has been a good one. They did two ‘slow’ / tech preview releases (well three if you count the 0.9 release). And now they are moving over (early in the development cycle). If they waited another year to do the real push, do you think the quality would be better?
Also, there is no reason you must move up. If Eclipse 3.7.1 is good for you, then you can continue to use that.
Iam Testing…
can i set the new eclipse to be less eye candy and look as before? the features themselves are ok. i just don’t like the blueish theme.