Themes for Team 3.0

Improve support for ISVs creating Team plugins

In 2.0 Team plugins could easily integrate into the workbench but contrary to 1.0 we didn't provide many re-useable Team specific views/actions. This meant that a substantial amount of work was required to write a plugin that has the same level of integration as CVS.

• Sync view re-design and API effort (M3)
  
• Improve team API (37705) (M5)
• Fix the problems with the Team hooks and team-private mechanism (37722)

• Make a generic repo view
• Create common team action sets
• Enhances project set support
• Add team events.

Work on the 3.0 plan items that affect Team

There are several other items on the Eclipse plan that is of much interest to the Team component. The following are those that we will be participating in:

• Support logical resources (37723) (M3)
• User settings (36965)
• Concurrency and background tasks (36957) (M3)
• Improve file encoding support (37933)
• Allow editors to open remote files (37935)
• Content-type-based editor lookup (37668)

Evolve the CVS plugin

We will continue to fix important bugs and provide key enhancements to the plugin.

• Integrate into the new sync view
• Provide annotate command
• Allows some CVS operations to run in the background
  • synchronizing
  • check outs
  • commits
  • tagging (versions and branches)
• Remove CVS plugin from platform SDK
  • make a CVS component separate from Team (bugzilla, web pages)
  • make install/update feature for CVS
• Improve repositories view (proposed)
  • re-work tag management
  • improve configure tags dialog
• Allow editing of remote files
  • Extend RemoteFileEditor to allow save (commit)
  • Expand repository view UI for opening files for viewing, editing, and external viewing
• Improve merging and branching workflows
• Improve initial sharing
  • show files that are being ignored
  • perform an add instead of the import
• Improve the performance of the CVS decorators (M4)
• Implement an improved revert mechanism (this will replace the 'copy all right to left' in compare editor)
• Support shallow commands (e.g. all commands that support -l)
• Permission support (see bug 20575)

• Request for comments (June 25th, 2003)
• Design proposal (July 18th, 2003)

• Request for comments (July 2nd, 2003)

Synchronize View and Team API

• Synchronize View Design proposal (September 28th, 2003)
• Team API plan (October 3rd, 2003)

• Progress support notes (September 25th, 2003)

2 developers (Michael Valenta, Jean-Michel Lemieux)

• Team API (5wks)
  • Migrating target management support for backwards compatibility story.
  • Refactoring Team core plugin for supporting versioning and non-versioning Team providers with more flexible mapping scenarios.
  • Move Synchronize View API into UI and finalize TeamSubscriber story.
  • Create WVCM TeamProvider and hooks for accessing the API.
  • Start working on a WVCM provider (e.g. either CVS, FTP, or Dav)..
  • Create a WVCM TeamSubscriber and Synchronize View components.
  • Document API and extend Team API plan to explain direction and usage patterns.
• Decorators (3 days)
  • Investigate poor performance of CVS decorators and in more general terms the decoration infrastructure provided by the workbench.
  • Investigate enabling CVS decorators by default when a project is shared/checked out.
  • Investigate showing all sync info in decorator (there are existing enhancement requests for this).
• Jaxp Conversion (1 day)
• UI Progress Support (4 days)
  • Move our Team specific view progress support for UI.
  • Help UI team implement progress services.
• Move CVS console onto generic console support (2 days)
• CVS Compare and replace with converted to Job mechanism. (2 days)
• Bug fixing (2 weeks)

2 developers (Michael Valenta, Jean-Michel Lemieux)

• Concurrency
  • User feedback improvements
    • progress messages
    • error handling and messages
  • Investigate maintaining context between backround jobs and views
  • Continue modifying CVS operations to run in the background and enable them by M4.
    
• Team API
  • Investigate JSR 147 and propose how it can be integrated into Eclipse.
    
• Synchronize View
  • Proper selection and expansion preservation.
  • Additional commands supported (delete, copy, paste, rename).
  • CVS: caching base/remote file contents for faster browsing of changes
  • CVS: decide on support for compare between local / remote and remote / remote.
    • currently uses a compare editor and requires multiple connections
  • Usability: Improved feedback for statistics and active filters.
  • Document API
    
• User Settings
  • Cooperate with Core and UI teams for implementation
    
• Logical to Physical
  • Outline a possible solution

• Work on bug backlog and inbox triage

3 developers (Michael Valenta (3wks), Dean Roberts (2wks), Jean-Michel Lemieux (4wks))

• User Settings (3 p/wk Michael)
  • Work on design based on feedback from the community.
  • Transfered implementation to Core team.
    
• Logical to Physical (1 p/wk Jean-Michel)
• Outline a possible solution (started but not complete)
  
• Concurrency (1 p/wk Jean-Michel)
  • Absorb core resources resource locking APIs and use for checkout.
  • Investigate impact of listeners running in jobs.
  • Enable other CVS operations to run in the background.
    • update from the sync view
    • commit from the sync view
  • Make CVS command framework thread-safe.
    
• Team API (1 p/wk Jean-Michel)
  • Investigate JSR 147 and propose how it can be integrated into current Team API. (deferred to M4)
    
• Synchronize View (API and replacement)(2 p/wk Dean & Jean-Michel)
  • Convert from SubscriberActions to using UI IActionFilter API.
  • Scalability improvements: calculate sync states in the background
  • By M3 the old sync view should be disabled
  • Propose solutions for loss functionality because compare is no longer all in the same view
    • Editor management (don't pollute work area with compare editors)
    • Browsing changes (in the old sync view you could Ctrl+. between tree viewer and compare editors)
  • Ensure performance is better that old sync view and that there are no major regressions.
  • Document API
    
• Work on bug backlog and inbox triage (1 p/wk Dean & Jean-Michel)

3 developers (Michael Valenta, Dean Roberts, Jean-Michel Lemieux)

• User Settings (3 p/wk)
  • Send out RFC
  • Prototype including examples of: (prototype was not released to HEAD, will be available for M3)
    • application settings (.config,
    • project settings (.classpath, .project)
    • non-project settings (CVs repo list file)
    • dialog settings (preferences)
  • Send out design proposal
    
• Logical to Physical (1 p/wk)
• Send out RFC
• Solicit input from community and products that have raised this issue as important for them
• Decide if a solution is possible
  
• Concurrency (2 p/wk)
  • fetching remote resources in the repo view in the background
  • refreshing the sync state in the background
  • checkout in the background
    
• Sync view replacement (2 p/wk)
  • Release synchronization API and UI components to support the new API. (tech-preview released and will have APIs available for M3)
  • Fix bugs as they are reported
  • Absorb and prototype action contribution enhancement plan item (deferred to M3)
    • enable key bindings for CVS actions
    • enable action overrides in sync view
    • enable key bindings for override actions
    • enable action contribution based on context
• Work on bug backlog and inbox triage (1 p/wk)