Jump to: navigation, search

Difference between revisions of "OTIndigo"

(Technical Details of Contributing to Indigo)
Line 130: Line 130:
 
** categorized
 
** categorized
  
* [[Image:Progress.gif]] <font color:red>Figure out the exact semantics of contribution definition (see [[Helios/Contributing_to_Helios_Build]]):</font>
+
* [[Image:Progress.gif]] <font color:red>Figure out the exact semantics of contribution definition (see [[Indigo/Contributing_to_Indigo_Build]]):</font>
** We will contribute our features to the '''Programming Languages''' category.
+
** We will contribute our features to the '''Programming Languages''' category, and OT/Equinox also to the '''EclipseRT Target Platform Components''' category.
** Assuming our contribution will look approximately like this:
+
** After first experiments with the b3 Aggregation Editor our contribution will look approximately like this:
 
   <?xml version="1.0" encoding="ASCII"?>
 
   <?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">
+
   <aggregator:Contribution xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:aggregator="http://www.eclipse.org/b3/2010/aggregator/1.0.0" label="Object Teams">
     <contacts name="Object Teams Build Team" email="stephan@..."/>
+
     <repositories location="http://download.eclipse.org/objectteams/updates/unstable">
    <features id="org.eclipse.objectteams.otdt" version="2.0.0.v20110111" repo="//@repositories.0">
+
      <features name="org.eclipse.objectteams.otdt.feature.group">
      <category href="helios.build#//@categories.1"/>
+
        <categories href="indigo.b3aggr#//@customCategories[identifier='Programming%20Languages']"/>
    </features>
+
      </features>
     <repositories location="http://download.eclipse.org/objectteams/updates/2.0/" label="Object Teams"/>
+
      <features name="org.eclipse.objectteams.otequinox.feature.group">
   </build:Contribution>
+
        <categories href="indigo.b3aggr#//@customCategories[identifier='Programming%20Languages']"/>
 +
        <categories href="indigo.b3aggr#//@customCategories[identifier='EclipseRT%20Target%20Platform%20Components']"/>
 +
      </features>
 +
     </repositories>
 +
    <contacts href="indigo.b3aggr#//@contacts[email='stephan@...']"/>
 +
   </aggregator: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>
 
:* [[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>
 
    
 
    
{{warning|The page [[Helios/Contributing_to_Helios_Build]] - although referred to from [[Indigo/Simultaneous_Release_Plan]] seems to be outdated. Instead we must use the [[Buckminster_Aggregatore_User_Guide|Buckminster b3 Aggregator]], yet, without a guide what exactly needs to be done for Indigo.}}
+
 
  
 
[[Category:Object Teams]]
 
[[Category:Object Teams]]

Revision as of 17:08, 26 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)
  • Ok green.gif subscribe to cross-project bugzilla inbox (sherrmann)
  • todo: provide contact details for build engineer (see below).

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 Indigo/Contributing_to_Indigo_Build):
    • We will contribute our features to the Programming Languages category, and OT/Equinox also to the EclipseRT Target Platform Components category.
    • After first experiments with the b3 Aggregation Editor our contribution will look approximately like this:
 <?xml version="1.0" encoding="ASCII"?>
 <aggregator:Contribution xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:aggregator="http://www.eclipse.org/b3/2010/aggregator/1.0.0" label="Object Teams">
   <repositories location="http://download.eclipse.org/objectteams/updates/unstable">
     <features name="org.eclipse.objectteams.otdt.feature.group">
       <categories href="indigo.b3aggr#//@customCategories[identifier='Programming%20Languages']"/>
     </features>
     <features name="org.eclipse.objectteams.otequinox.feature.group">
       <categories href="indigo.b3aggr#//@customCategories[identifier='Programming%20Languages']"/>
       <categories href="indigo.b3aggr#//@customCategories[identifier='EclipseRT%20Target%20Platform%20Components']"/>
     </features>
   </repositories>
   <contacts href="indigo.b3aggr#//@contacts[email='stephan@...']"/>
 </aggregator:Contribution>
  • Glass.gif Given the above will be referenced from the main indigo.build file, will this suffice to include our features into aggregation?