Difference between revisions of "OTIndigo"

Revision as of 15:08, 16 December 2010

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

• 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)
• subscribe to cross-project bugzilla inbox (sherrmann)
• provide contact details for build engineer (see objectteams.b3aggrcon).

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
• Eclipse-wide strategy for dealing with all kinds of exceptions
  • Equinox/p2/Proposals/Install_Capabilities
  • see also bug 316702
• further discussion (process & technology)
  • API requests in bugzilla
  • extended friend mechanisms?
    • integrate with API tools?
    • establish communication protocol between teams?

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 the following exceptions, is unpacking still needed?
    • otdt: changing to jarred install seems to work out of the box, more testing needed
    • otdt.ui.help: got it to work with the little patch in bug 329806
    • otdt.samples: could be difficult to persuade the pde.ui.samples extension point to work off a jarred plug-in.

    I filed bug 332748 to track this last reason for unpacking.

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.
  • actually p2 touchpoints don't currently support smooth installation of several plug-ins using adaptor hooks (see bug 329784).
  • OTDT's aspect bindings interfering with other features. Shouldn't happen, if it happens we can fix on short notice.
• planning to cross-test the OTDT with other bytecode weaving plugins installed
  • These are not part of Indigo: AJDT, Greclipse, Scala IDE
  • any weaving bundles in Indigo?

License text consistency

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

Be a good Eclipse Citizen ... and document it

Engage Community

• New&Noteworthy documents are available at each milestone (cumulative up-to release)
  • e.g.: 0.7.0 N&N

Usability

• Mimic and extend JDT's lead.

Performance

• todo

Test Localization

• todo

Enable Use with All Languages

• todo awaiting users from non-western locals for input

Builds

• see OTBuilding

Ramp Down Planned and Defined

• todo

Accessibility

• todo

Unit Tests

• currently more than 45400 tests
  • publish test results?

API Policy

• will follow general rules concerning x-internal etc.

Retention Policy

• todo

Project Metrics

• docuware from 0.7.0 release revies should be a good starting point

Technical Details of Contributing to Indigo

• As documented in OTBuilding the automated build includes creating a deployable p2 repository with these properties
  • signed
  • with pack200 files
  • accumulative meta data per minor release
  • categorized

• Our contribution has been committed by following the steps in Indigo/Contributing_to_Indigo_Build:
  • We are contributing our features to the Programming Languages category, and OT/Equinox also to the EclipseRT Target Platform Components category, see objectteams.b3aggrcon
• Two issues were fixed during joining the aggregation build:
  • Our pack200 files were affected by incompatibility between JDK 5 & 6 (see bug 311469#6 ff.).
  • The platform filter of our fragment org.eclipse.objectteams.otequinox.sunjvm had a typo which was never reported (see bug 329984, bug 329985).