Jump to: navigation, search

Difference between revisions of "OTIndigo"

(New page: The Eclipse Object Teams Project intends to join the Indigo release train. Here are the details wrt the [http://eclipse.org/helios/planning/EclipseSimultaneousRelease.php Eclipse Simul...)
 
Line 1: Line 1:
 +
<css>
 +
ul { list-style-image: url(http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/arrow.gif); }
 +
</css>
 +
 
The Eclipse Object Teams Project intends to join the [[Indigo]] release train.
 
The Eclipse Object Teams Project intends to join the [[Indigo]] release train.
 
Here are the details wrt the [http://eclipse.org/helios/planning/EclipseSimultaneousRelease.php Eclipse Simultaneous Release] document.
 
Here are the details wrt the [http://eclipse.org/helios/planning/EclipseSimultaneousRelease.php Eclipse Simultaneous Release] document.
Line 77: Line 81:
 
===License text consistency===
 
===License text consistency===
 
* [[Image:Ok_green.gif]] Release 0.7.0 already consistently uses the June 15, 2010 version of about texts etc.
 
* [[Image:Ok_green.gif]] Release 0.7.0 already consistently uses the June 15, 2010 version of about texts etc.
 +
 +
[[Category:Object Teams]]

Revision as of 08:50, 22 August 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

  • todo: express statement of intent in the Portal

Planning

  • Progress.gif update project plan

IP Documentation

  • Progress.gif ongoing

Release Review

  • (typically at RC2)

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

Communication

  • Ok green.gif subscribe to cross-project mailing list (sherrmann)
  • todo: subscribe to corss-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
  • Glass.gif 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

  • Progress.gif mostly done.

Version Numbers

  • Ok green.gif 4-part version numbers are consistently used

OSGi bundle format

  • Ok green.gif all plugins are true OSGi bundles.

Execution Environment

  • Ok green.gif all bundles have BREE set to J2SE-1.5

Signing

  • Ok green.gif all jars are signed on build.eclipse.org

Jarred Bundles

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

Re-use and share

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

Capabilities

  • todo

Support Translations

  • Progress.gif string externalization is mostly done, participation in babel TODO

Excel in NL support

  • Glass.gif investigate where this would make sense

Branding

  • Ok green.gif About dialog icon with details is in place.

Do No Harm

  • Glass.gif 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

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