Team/CVS plan for the 3.2 Release

item is under development

item is finished

[>3.2] item is deferred

Themes for Team/CVS 3.2

The overall themes for this release are detailed below:

Bug 37723
Requirements identified during 3.1 can be found here.
Publish proposed solutions
- work in progress is found here
Logical Model Decoration by Resource based tools (i.e. repositories)
- full adaptable support in decoration manager
- sub-file level dirty decoration
- label updating of model elements without a one-to-one mapping to resources
Compare/Merge
- Logical model integration into the synchronize view
- Modify CVS synchronize pages to support logical model views
- Logical model compare editor support
- Support for head-less model merging
CVS Operations
- modification of CVS operations to use model merging support for head-less and manual compare/merge
- Support for the display of logical model elements hierarchies in non-synchronization views.
Patching
- Support multi-select in create/apply patch
- Support resource selection in Create Patch
- Integrate logical model support into apply patch

Logical Model Integration
- Investigate support for decorators
  - Patch applied to workbench for adaptable decorator support (bug 86159)
- Investigate support for team operation participation
  - Prototype developed but not yet available in repository

Fostering Community Involvement
- Several patches applied to CVS. Thanks everyone:

Draft proposed solutions document
Participate in cross-team items
- Generic Navigator
- Problems View
- User Roles

Team Operation Participation
- Need to identify proper plugin for extension point (bug 108352)
- Determine relationship between Participants, LTK and Generic Navigator
Label Decoration with repository dirty state
- Need to add API to ResourceMapping to support decoration of sub-file level model elements.
- Need to add support for label update of model elements (bug 86493)
Investigate manual merging of Logical Models
- Logical models in the synchronize view
- Logical model elements in Compare editors
Improve Patching

Displaying Logical Models
- Investigate how to use Common Navigator framework to support the display of team context
Headless Merging

Define API for headless model merging
Modify CVS to perform headless merge operations (e.g. update, replace) using model API.

Investigate possible ways to allow users to browse logical models in a repository

Displaying Logical Models
- Intergrate team contexts in Common Navigator (gated by Common Navigator)
Model Level Merging

Use Team contexts and Common Navigator to provide manual merging infrastrucuture (gated by Common Navigator)
Do any additional work to ease the implementation of merge support by repository or model providers

Depending on the rsults of the M3 investigation, provide facilites to support remote browsing

See the Team Support for Logical Model Integration document for a description of the state of the Team API as of 3.2. M4.

Displaying Logical Models
- Support display of team-aware models in views, dialogs and editors
- Support different operation types (i.e. merging, commit, sync)
- Support model actions in team views
- Support team-state decoration in model views (i.e. outside the context of a team operation)
Model Level Merging

Finalize Generic History view
- support page based view
- provide default page implementation
- provide CVS hsitory with no regressions from CVS view
Remote Browsing
- Support remote browsing of models using EFS and IResource
- Support loading of workspace from remote model view
  - support partial loading of models

Operation Validation
- Provide mechanism for higher level models to validate operations performed by lower level models
- Convert resource operations in the IDE plugin to use the validation mechanism