Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
OTIndigo
Revision as of 10:58, 22 August 2010 by Unnamed Poltroon (Talk)
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)
- 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
- 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 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>