How do we know ? Well for one thing I finally have time to start blogging...;-). This is just the first of many posts I expect to be making over the summer (and likely the least technical).
After almost 3 years of design and development the next version of Eclipse is ready for you to start using.
Is it perfect yet ? No, see the Known Issues page here but we are sure that none of these issues cannot be addressed during the 4.2 cycle. It's now time to pass the ball over to the community; we need your input to make this version of Eclipse even better..
The current PMC plans are that 4.2 should be the base platform for the Juno release and it will be our primary focus for 4.2 to ensure that this happens. Any defects found by the release train components will be top priority (actually any component, release train or not, if you're willing to spend the time testing we're ready to spend the time fixing your issues). Here's how you can help:
Testing Your Components:
We've already done our own 'ad hoc' testing of various components (CDT, Mylyn...) but only the actual component team knows enough about their features to ensure that our compatibility coverage is 100%. Testing your component in Eclipse 4 is easy (if it weren't I'd likely be updating my resume rather than writing this blog post...;-), even for something like the CDT the testing time required was under 3 hours:
- Download Eclipse 4.1
- Use it as you would normally and install / check out your component
- Run through a test of your component's features
- Open any perspectives and check that everything's there
- Ensure that all views / editors work correctly
- Check the part's menu and toolbar items to make sure they're OK
We're here for you:
If you encounter any issues which prevent you from testing your component feel free to contact me directly (firstname.lastname@example.org) and I'd be happy to help out in any way (including working through the issues directly with you on the phone as I did with Chris for CDT, here's his blog entry about it).
Report any defects against Eclipse -> Platform -> UI as you normally would (setting the target milestone to 4.1.1 will help us triage them). As I said above these will receive preferred treatment...It is worth noting that we are well positioned for this, the compatibility layer and the e4 core are much more compartmentalized so our ability for find and fix defects is faaar faster than the equivalent in the 3.x stream.
Also feel free to join us on IRC at '#eclipse-e4' or by posting to the mailing list 'email@example.com' to join in discussions about where we should be taking the 4.x stream beyond simply being compatible or just to share anything Eclipse 4 related.
I'm really looking forward to this year and seeing Eclipse 4 mature into the IDE of the future...