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.
Difference between revisions of "OTIndigo"
(css styling) |
|||
Line 1: | Line 1: | ||
<css> | <css> | ||
− | ul { list-style-image: | + | /* set list bullet to circle (de-emphasize) */ |
+ | ul { list-style-image:none; list-style-type:circle;} | ||
</css> | </css> | ||
Line 21: | Line 22: | ||
===Communication=== | ===Communication=== | ||
* [[Image:Ok_green.gif]] subscribe to cross-project mailing list (sherrmann) | * [[Image:Ok_green.gif]] subscribe to cross-project mailing list (sherrmann) | ||
− | * '''todo''': subscribe to | + | * '''todo''': subscribe to cross-project bugzilla inbox |
* '''todo''': provide contact details for build engineer | * '''todo''': provide contact details for build engineer | ||
Revision as of 10:16, 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.
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