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.
OTIndigo
Revision as of 09:50, 22 August 2010 by Stephan.cs.tu-berlin.de (Talk | contribs)
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 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
- 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