JDT Core 3.8 Plan

Last revised $Date: 2011/12/19 10:22:37 $

This plan is under continuous refinement. Please send comments about this plan to the jdt-core-dev@eclipse.org developer mailing list.

Overall Goals

This section lists the goals for Eclipse 3.8 for the JDT Core component as listed on the Eclipse Project 3.8 Draft Plan.

[1] Scaling up. Monitor overall performance and memory consumption which includes the addition of new performance tests for new features.

[2] Design for Extensibility. Provide APIs for clients where needed and fix critical bugs.

[3] Ease of Use. Make sure we run on the e4 compatibility layer and deliver new productivity features.

[4] Technology Trends. Add support for Java 7. Start to work on Java 8 support.

Work Items

This section lists the possible work items for Eclipse 3.8 for the JDT Core component with the [corresponding theme]. Some of those items have a higher priority than others.

• Java 7 [4]

  • finish the work on Java 7 support 20 weeks
  • backport the Java 7 support to 3.7.1 6 weeks

• Java 8 [4]

  • start to work on Java 8 features 40 weeks

• Adopt New Platform Features [3]

  • help productizing Eclipse 4.2 4 weeks
    • make sure that we smoothly run on Eclipse SDK 3.8 and 4.2
    • provide feedback on outstanding issues to the Platform UI team
    • test our bundles against 4.2

• API [2]

  • None at this point

• Performance And Memory Consumption [1]

  • constantly watch performance test results and act when red
  • continue to provide new tests
  • improve code coverage
  • Improve performances for classpath resolution

• Miscellaneous

  • migration to Git all: 3 weeks in total

• General Items

  • 3.7.x maintenance work [all]
  • look at bugs with patches and review those
  • Improved null analysis via null annotations (bug 186342)
  • Support for pre-built indexes (bug 356620)
  • A couple of new enhancements in the code formatter

Java 7 [4]

• finish the work on Java 7 support 20 weeks
• backport the Java 7 support to 3.7.1 6 weeks

General Items

• [2] 3.7.1 maintenance work [all]
• [2] bug fixing [all]
• [3] 3.8 planning [olivier]

Permanent Items

• bugzilla inbox tracking
• bug fixing (fixed) (all) (unresolved) (resolved)
• watch performance tests

Miscellaneous

• prepare Git migration all: 3 weeks in total

General Items

• [2] 3.7.1 maintenance work [all]
• [2] bug fixing [all]
• [3] 3.8 planning [olivier]

Permanent Items

• bugzilla inbox tracking
• bug fixing (fixed) (all) (unresolved) (resolved)
• watch performance tests

Miscellaneous

• Done with Git migration all: 3 weeks in total

General Items

• [2] 3.7.2 maintenance work [all]
• [2] bug fixing [all]
• [3] 3.8 planning [olivier]

Permanent Items

• bugzilla inbox tracking
• bug fixing (fixed) (all) (unresolved) (resolved)
• watch performance tests

General Items

• [2] 3.7.2 maintenance work [all]
• [2] bug fixing [all]
• [M4] [compiler][null] Using annotations for null checking: 186342[Satyam]

Permanent Items

• bugzilla inbox tracking
• bug fixing (fixed) (all) (unresolved) (resolved)
• watch performance tests

General Items

• [2] 3.7.2 maintenance work [all]
• [2] bug fixing [all]
• [M5] Make it possible to provide indexes for defined libraries: 356620[Satyam]
• [M5] Improved support for null annotations based null analysis: 365519 365983 365836 365662 365531 365835 365992 366003
• [M5] Resource leak warning improvements: 358903 360908 362332 365710
• [M5] Detecting null field reference 247564
• [M5] Formatter improvements: 303519

Permanent Items

• bugzilla inbox tracking
• bug fixing (fixed) (all) (unresolved) (resolved)
• watch performance tests

• find a bug report
• report a bug