| [eclipse-dev] Planning Meeting Notes - March 9, 2011 |
--------
Status
--------
JDT UI:
- added API to enable '?' button in lightweight refactoring dialogs
- EclipseCon preparation
- bug fixing
JDT Text:
- break and continue keywords and labels are now hyperlinks
(Ctrl+click) and F3 targets
- working on indentation issues in string continuations
- bug fixing
JDT Core:
- bug fixes/triage
- 3.7M6 verification
- Java 7: worked on try-with-resources implementation:
- first draft should be released by the end of the week
- one more fix will go in for M6:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=339139
- few fixes around null analysis and code generation
Ant:
- 3.7M6 testing
- inbox triage
- bug fixing
Debug:
- 3.7M6 testing
- continued investigation of thread / debug context problems
with stepping and heavily multi-threaded applications
- inbox triage
- bug fixing
PDE:
- added new Api Use Scan Problem Task (332763)
- 3.7 M6 test pass
SWT:
- new system menu API released
- DROP_DOWN calendar implemented for DateTime on GTK, so now
available on all platforms
- touch and application menu API changed slightly
- aero work continuing, will not be ready for 3.7M6
- various bug fixes
User Assistance:
- help Servlet API committed
- bug fixing and testing
Performance:
- 3.7:
- N20110305-2000: nothing new
- N20110303-2000: nothing new
Platform Workspace:
- inbox tracking
- adjusting the 3.7 plan, preparing the 3.7 M7 plan
Rel Eng.:
- moved to new Orbit build
- test builds with 3.7M6 test candidate bundles
- test builds for code coverage with JaCoco:
- working on issues with JaCoco committers
- https://bugs.eclipse.org/241254
- test builds on Hudson at eclipse.org. Some interesting numbers:
- time to complete running 68,000 JUnit tests:
eclipse.org IBM
Linux 7 hours 6 minutes 6 hours 7 minutes
Mac 9 hours 43 minutes* 4 hours 52 minutes
Windows 7 hours 43 minutes 6 hours 57 minutes
- current remaining numbers of test failures:
- Linux 21
- Windows 63
- Mac 100's*
* some infrastructure issues remain - thus some test suites hit the
2 hour timeout limit and extend the test run
.