Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
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 [[ | + | * [[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. |
− | ** | + | ** 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"?> | ||
− | < | + | <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> | |
− | <repositories | + | <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> | ||
:* [[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> | ||
− | + | ||
[[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.
Contents
Do the basics ... early
- todo: express statement of intent in the Portal
Planning
IP Documentation
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)
- 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
- 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
Version Numbers
OSGi bundle format
Execution Environment
Signing
Jarred Bundles
Capabilities
- todo
Support Translations
Excel in NL support
Branding
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.
- other feature providing a patch to
License text consistency
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
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
API Policy
Retention Policy
- todo
Project Metrics
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
- 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>