OTIndigo

The Eclipse Object Teams Project intends to join the Indigo release train. Here are the details wrt the Eclipse Simultaneous Release document.

Do the basics ... early

• todo: express statement of intent in the Portal

Planning

• update project plan

IP Documentation

• ongoing

Release Review

• (typically at RC2)

Play well with others ... to be in common repository

Communication

• subscribe to cross-project mailing list (sherrmann)
• todo: subscribe to cross-project bugzilla inbox
• todo: provide contact details for build engineer

API

Here is where the fun starts :)

• todo: document non-standard usage
  • usage of internal classes
  • aspect binding to bundle
    • decapsulation
    • interception
  • patch feature for org.eclipse.jdt.core
• discuss how to handle the above
  • API requests in bugzilla
  • extended friend mechanisms?
    • integrate with API tools?
    • establish communication protocol between teams?
  • transparency for end users, see bug 316702!

Message Bundles

• mostly done.

Version Numbers

• 4-part version numbers are consistently used

OSGi bundle format

• all plugins are true OSGi bundles.

Execution Environment

• all bundles have BREE set to J2SE-1.5

Signing

• all jars are signed on build.eclipse.org

Jarred Bundles

• most bundles are jarred
  • check these exceptions: otdt, otdt.ui.help, otdt.samples, is unpacking still needed?

Re-use and share

• the only external dependency org.apache.bcel is consumed from Orbit.

Capabilities

• todo

Support Translations

• string externalization is mostly done, participation in babel TODO

Excel in NL support

• investigate where this would make sense

Branding

• About dialog icon with details is in place.

Do No Harm

• potential incompatibilities could arise from
  • other feature providing a patch to org.eclipse.jdt.core, too. => incompatible
  • other feature applying bytecode weaving, too. Needs investigation, should be possible.
  • OTDT's aspect bindings interfering with other features. Shouldn't happen, if it happens we can fix on short notice.

License text consistency

• Release 0.7.0 already consistently uses the June 15, 2010 version of about texts etc.