Back to Archived Releases

Team 3.1 Plan platform team integration framework

Themes for Team 3.1

item is under development

item is finished

[>3.1] item is deferred

The overall themes for this release are detailed below:

• Built to last
• ValidateEdit/Save article / test-plan

• Simple to use
• Change Sets
• Expose notion of resources that are changed together as a logical change.
• Could be hooked into validateEdit mechanism, but with a symbolic comment
• A hint that certain resources should be checked in together
• Local History support for rollback - Investigate local history synchronize participant example and allow baselining local history by timestamp with a symbolic name. You could then rollback a refactoring. This could be coupled with the change set support.
• Scheduled synchronizations provide too many errors and too many log messages.
  
• Allow un-docking synchronizations from the synchronize view into their own views.
  
• Compare editor management - should compare editors be automatically closed, or could a user override the default that the compare editor is always re-used.
  
• Rich client platform
• Refactor FTP and DAV for use in RCP applications.
• Large-scale development
• Support logical resources (37723). See the Implementation Plan for more details.
  
• Team Policies (71126) [Large-scale development]
• Bug tracking integration (synchronize view, history view) browse bugs from within Eclipse.

3.1 Development Effort - Milestone 2 (Friday Sept 24th, 2004)

• Logical to Physical [Jean-Michel]
  
  
  • Scope the problem
    
  •   Send out RFC
  • Solicit input from community and products that have raised this issue as important for them
  • Decide on what will be done for 3.1
    [Note: we have scoped the problem and have decided to split the plan item into two separate issues. The first will remain as "Support Logical Resources" and the second will be called "Support mapping between a logical view to physical files on disk.". For 3.1 we are planning to address the mapping plan item only.]
    


• FTP/WebDAV [Mike]
  • Code cleanup and refactor for use in RCP
  • Consider the future state of these plugins (i.e. they are currently not production quality)
    [Note: We have posted mail to the WTP http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg00071.html but haven't made a decision about were it will live yet.]
    
    
• Bug Tracking Integration [Silvio]
  
  
• Investigation into how we could integrate simple bug tracking into Team
• Some possible use-cases are:
• generic action support that would allow browsing a bug from the history view, or commit sets.
• commit comment selection from a list of bugs
• configuration of bug systems per project (you may be working on different projects with different bug system)
• update file list in a bug and then close the bug from within Eclipse
• attach a patch to the bug
• query bugs
  
  
[Note: We are experimenting with bug integration with a bugzilla reference. Nothing to release yet.]

3.1 Development Effort - Milestone 3 (Friday Nov. 5, 2004)

• Logical to Physical [Jean-Michel]
• Continue with community review
  
• Propose an implementation plan
• Start implementation
  
• Move commit set support from CVS into Team [Mike]
• Rename "Commit Sets" to "Change Sets" to be less CVS specific
• Allow other synchronize participants to use incoming/outgoing change set support
• Enable objectContributions in the Synchronize View
• Error handling for background tasks [Jean-Michel]
• Background synchronize jobs that fail because of lost connections can continue to fail. We should provide better disconnected use of scheduled tasks.
• This include the quikdiff support that throws errors when disconnected.

3.1 Development Effort - Milestone 4 (Friday Dev. 17, 2004)

• Logical to Physical [Jean-Michel]
• Provide Runtime and Workbench patches for enabling adaptable contributions
• Provide patches to Resources for IResourceMapper APIs
  

3.1 Development Effort - Milestone 5 (Friday Feb. 18, 2005)

• Logical to Physical [Michael]
• Convert CVS operations to use IResourceMapper
• Prepare document for model providers and repository providers on how to use the new ResourceMappings

3.1 Development Effort - Milestone 6 (Friday Apr. 1, 2005)

• Logical to Physical [Michael]
• Investigate APIs needed to display ResourceMapping in static viewers
• Investigate composite mappers (e.g. working sets)
• Local History Synchronize Participant [Michael]
• Allowing roolback or time-related file changes
• Use the change groupings to show related changes