Jump to: navigation, search

Difference between revisions of "OTIndigo"

(css styling)
Line 82: Line 82:
 
===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.
 +
 +
 +
==Be a good Eclipse Citizen ... and document it==
 +
===Engage Community===
 +
* [[Image:Ok_green.gif]] New&Noteworthy documents are available at each milestone (cumulative up-to release)
 +
** e.g.: [http://www.eclipse.org/objectteams/pages/new_in_0.7.html 0.7.0 N&N]
 +
 +
===Usability===
 +
* [[Image:Ok_green.gif]] 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===
 +
* [[Image:Ok_green.gif]] see [[OTBuilding]]
 +
 +
===Ramp Down Planned and Defined===
 +
* '''todo'''
 +
 +
===Accessibility===
 +
* '''todo'''
 +
 +
===Unit Tests===
 +
* [[Image:Ok_green.gif]] currently more than 45400 tests
 +
** [[Image:Glass.gif]] publish test results?
 +
 +
===API Policy===
 +
* [[Image:Progress.gif]] will follow general rules concerning x-internal etc.
 +
 +
===Retention Policy===
 +
* '''todo'''
 +
 +
===Project Metrics===
 +
* [[Image:Progress.gif]] docuware from 0.7.0 release revies should be a good starting point
 +
 +
==Technical Details of Contributing to Indigo==
 +
* [[Image:Ok_green.gif]] 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
 +
 +
* [[Image:Progress.gif]] <font color:red>Figure out the exact semantics of contribution definition (see [[Helios/Contributing_to_Helios_Build]]):</font>
 +
** We will contribute our features to the '''Programming Languages''' category.
 +
** Assuming our contribution will look approximately like this:
 +
  <?xml version="1.0" encoding="ASCII"?>
 +
  <build:Contribution xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:build="http://www.eclipse.org/amalgam/2008/build" label="Object Teams">
 +
    <contacts name="Object Teams Build Team" email="stephan@..."/>
 +
    <features id="org.eclipse.objectteams.otdt" version="2.0.0.v20110111" repo="//@repositories.0">
 +
      <category href="helios.build#//@categories.1"/>
 +
    </features>
 +
    <repositories location="http://download.eclipse.org/objectteams/updates/2.0/" label="Object Teams"/>
 +
  </build:Contribution>
 +
:* [[Image:Glass.gif]] <font color=red>Given the above will be referenced from the main indigo.build file, will this suffice to include our features into aggregation?</font>
 +
 
  
 
[[Category:Object Teams]]
 
[[Category:Object Teams]]

Revision as of 09:58, 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 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
  • 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.


Be a good Eclipse Citizen ... and document it

Engage Community

  • Ok green.gif New&Noteworthy documents are available at each milestone (cumulative up-to release)

Usability

  • Ok green.gif 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

Ramp Down Planned and Defined

  • todo

Accessibility

  • todo

Unit Tests

  • Ok green.gif currently more than 45400 tests
    • Glass.gif publish test results?

API Policy

  • Progress.gif will follow general rules concerning x-internal etc.

Retention Policy

  • todo

Project Metrics

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

Technical Details of Contributing to Indigo

  • Ok green.gif 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
  • Progress.gif Figure out the exact semantics of contribution definition (see Helios/Contributing_to_Helios_Build):
    • We will contribute our features to the Programming Languages category.
    • Assuming our contribution will look approximately like this:
 <?xml version="1.0" encoding="ASCII"?>
 <build:Contribution xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:build="http://www.eclipse.org/amalgam/2008/build" label="Object Teams">
   <contacts name="Object Teams Build Team" email="stephan@..."/>
   <features id="org.eclipse.objectteams.otdt" version="2.0.0.v20110111" repo="//@repositories.0">
     <category href="helios.build#//@categories.1"/>
   </features>
   <repositories location="http://download.eclipse.org/objectteams/updates/2.0/" label="Object Teams"/>
 </build:Contribution>
  • Glass.gif Given the above will be referenced from the main indigo.build file, will this suffice to include our features into aggregation?