Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Planning Meeting Notes - Sept 1, 2004 
Team/CVS
- all 3.0.1 bug fixes have been submitted
- performance tests for CVS have been ported to new performance framework
- M2 milestone plan has been posted for CVS 
(http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/cvs3.1/plan.html):
    *  Performance and Memory [Mike]
          o Create a set of performance tests for benchmark framework
          o Investigate ways to reduce memory usage for CVS metadata 
caching
    * Commit Set [Mike]
          o allow the user to create, manage outgoing commit sets
          o drag n' drop files between outgoing sets
          o active set get new changes
          o merge sets by dragging one set into another (this could also 
merge the set names)
    * Update prompter [Jean-Michel]
          o remove the automatic prompter
          o assign wizard to keybinding instead
    * Annotate [Silvio]
          o  add preference so that view can appear in a user defined 
perspective
          o fetch annotations in the background
    * Decorators [Jean-Michel]
          o add support for color and fonts in CVS decorators
          o add support for configuring commit set decoration
          o improve preview support
- M2 milestone plan has been posted for Team 
(http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.1/plan.html):
    *  Logical to Physical [Jean-Michel]
                o Scope the problem
        o Send out RFC
        o Solicit input from community and products that have raised this 
issue as important for them
        o Decide on what will be done for 3.1
    * FTP/WebDAV [Mike]
        o Code cleanup and refactor for use in RCP
         o Consider the future state of these plugins (i.e. they are 
currently not production quality)
    * Basic Bug Tracking Integration [Silvio]
        o Investigation into how we could integrate simple bug tracking 
into Team
        o Some possible use-cases are:
                        o generic action support that would allow browsing 
a bug from the history view, or commit sets.
                        o commit comment selection from a list of bugs
                        o configuration of bug systems per project (you 
may be working on different projects with different bug system)
                        o update file list in a bug and then close the bug 
from within Eclipse
                        o attach a patch to the bug
                        o query bugs

Cheers,
Jean-Michel

Back to the top