Back to Archived Releases

CVS platform cvs support

Themes for CVS 3.0

item is under development

item is finished

[>3.0] item is deferred

The overall themes for this release are detailed below:

• responsiveness
• improved user experience
• fix major bugs that are getting in the way of Eclipse users using CVS

The top work items are:

• Responsiveness
• Implement concurrency support in CVS data structures and sync caches.
• Allow many CVS operations to run in the background.
  
• User Experience
  
• Improve initial sharing wizard.
• Improve merging and branching workflows.
• [>3.0] repositories view usability fixes.
  
• [>3.0] improve tag management (branches and versions).
  
• Integrate into the new Team Synchronize APIs
• Provide background refresh with repository.
• Harmonize merging and synchronizing.
  
• Improved security and out-of-the box experience with integrated SSH2 support
• Replace current SSH1 plug-in with integrated SSH2 support.
• Provide key generation within Eclipse.
• Provide connection re-use to speed-up authentication and the overall responsiveness of the CVS plug-in.
  
• Performance and stability
• Ensure that our CVS client is up-to-date with latest CVS releases.
• Provide benchmarks against command line client.

3.0 Development Effort - Milestone 9 (Friday May 7, 2004)

• Over 100 bugs marked for M9!
• Encoding support in CVS (22 votes in this bug!)
  • log message should respect encoding
  • file contents should respect encoding
  • other areas affected?
• SSH2
  
• responsiveness (cancellation, password prompting...)
• deadlock with multiplexed stream -
  
• CVS breakage friendly
  
• (support checkout/commit/update if we can't parse output)
• Support checkout even if repo view browing doesn't work
• Enumerate which CVS plug-in actions can be used even if the server version isn't supported
• Improve warning message for incompatible CVS server version
• Password/repository persistence
  
• * is it safe to persist passwords between sessions in the keyring file?
  
• * could the keyring be password protected?
  
• * could the repository locations be persisted in the CONFIG scope?
  
• (if we have time) Enhancements:
  
• CVS date tag support (3 days)
• CVS change logs (3 days)
• CVS update -r (switch to another branch) (3 days)
  
• CVS standard repos (2 days)
  

3.0 Development Effort - Milestone 8 (Friday March 26, 2004)

• Improve support for multiple CVS server versions (deferred to M9 - is a P1 item for M9 though)
  
• Support checkout even if repo view browing doesn't work
• Enumerate which CVS plug-in actions can be used even if the server version isn't supported
• Improve warning message for incompatible CVS server version
• Improve sharing wizard to allow resolving projects shared when there is existing
  
• Adapt to new user settings work.
• SSH2 support
• Provide solution for outstanding deadlock PR (finished in M9).
• Enable SSH2 for default.
• Improve key generation and exporting workflows
• Inbox monitoring and bug fixing - we have a big backlog and will have to spend one week each going through to classify and fix the important bugs.
  

3.0 Development Effort - Milestone 7 (Friday February 13th, 2004)

• Finalize SSH2 support
• Investigate outstanding deadlock PR.
• Provide extssh backwards compatibility support.
• Enable SSH2 for default by M7.
• Inbox monitoring and bug fixing
  

What's new prior to M7?

• Annotate command
• History view linking to active editor
• Synchronize View integration and many improvements
• Add instead of import used when initially sharing a project
• Simplification of Checkout operations
• CVS decorators improved by patching UI decorator code
• CVS is now a separate component with it's own bugzilla and mailing lists