| <!-- ###### Header ###### --> |
| <script language="JavaScript1.3" src="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/cvs-header.js"></script> |
| <!-- ###### Body Text ###### --> |
| |
| <div id="bodyText"> |
| <p>Back to <a href="../archivedReleases.php">Archived Releases</a></p> |
| <h1>CVS 2.1 Plan</h1> |
| <table> |
| <tr> |
| <td width="98%"> <h4>2.0.1 Maintenance effort</h4> |
| <ul> |
| <li>Corresponding sources are released in branch "R2_0_1".</li> |
| <li>Plug-in revision ID got changed to "2.0.1". </li> |
| <li> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.0.1&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| Bugs fixed in 2.0.1</a></li> |
| <li> To find the latest Eclipse development on the 2.0.1 branch please |
| go <a href="http://64.38.198.171/downloads">here</a></li> |
| </ul> |
| <h4> 2.1 Development Effort - Milestone 1 (September 20, 2002)</h4> |
| <ul> |
| <li> Bug fixing - Fixing backlog of defects discovered in the 2.0 release |
| ( <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M1&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M1 bugs to be fixed,</a> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1&target_milestone=2.1+M1&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M1 bugs already fixed</a>) </li> |
| <li>Investigation of <a href="modules.html">improved module support</a> |
| (i.e. modules defined in CVSROOT/modules) |
| <li>New features: |
| <ul> |
| <li>parameterization of EXT connection method</li> |
| <li>"Quick Sync" button added to CVS action set</li> |
| <li>"Team > Commit" prompt for un-added resources</li> |
| </ul> |
| </li> |
| </ul> |
| <h4>2.1 Development Effort - Milestone 2 (October 18, 2002)</h4> |
| <ul> |
| <li> Bug fixing - Fixing backlog of defects discovered in the 2.0 release |
| ( <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M2&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M2 bugs to be fixed,</a> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M2&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M2 bugs already fixed</a>) </li> |
| <li>Investigation of support for Eclipse Release Engineering</li> |
| <li>Investigation of CVS Repository View usability improvements</li> |
| <li>New features: |
| <ul> |
| <li><a href="modules.html">Improved module support</a></li> |
| </ul> |
| </li> |
| </ul> |
| <h4>2.1 Development Effort - Milestone 3 (November 15, 2002)</h4> |
| <ul> |
| <li> Bug fixing - Fixing backlog of defects discovered in the 2.0 release |
| ( <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M3&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M3 bugs to be fixed,</a> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M3&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M3 bugs already fixed</a>) </li> |
| <li>Investigate enhancing project sets to support project set comparison |
| and/or recursive loading</li> |
| </ul> |
| <h4>2.1 Development Effort - Milestone 4 (December 13, 2002)</h4> |
| <ul> |
| <li> Bug fixing ( <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M4&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M4 bugs to be fixed,</a> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M4&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M4 bugs already fixed</a>) </li> |
| <li>Performance improvements</li> |
| <li>Team support for flexible project structure</li> |
| <li>CVS support for edit/unedit</li> |
| <li>Investigate SSH2</li> |
| </ul> |
| <h4><a name="Milestone_Planning"></a> 2.1 Development Effort - Milestone |
| 5 (February 7, 2003)</h4> |
| <ul> |
| <li> Bug fixing ( <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M5&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M5 bugs to be fixed,</a> <a href="http://dev.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=VCM&target_milestone=2.1+M5&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=Fixed+by+me&newqueryname=&order=Reuse+same+sort+as+last+time"> |
| 2.1 M5 bugs already fixed</a>) </li> |
| <li>Performance improvements</li> |
| <li>CVS Repository View refinements</li> |
| <li>Usability</li> |
| </ul> |
| <p> To see how bugs are prioritized and categorized for VCM, check out |
| <a href="bug_tracking.html">VCM Bug Tracking</a> </p> |
| <h4>2.1 and beyond</h4> |
| This is a list of areas that we have identified as potential work items |
| for CVS in Eclipse 2.1 and beyond. Please note that this list is what |
| has been identified so far as potential work areas and does not represent |
| a commitment from the VCM team. See <a href="#Milestone_Planning">milestone |
| planning</a> for curent work items. |
| <p><b>2.1 Items</b></p> |
| <ol> |
| <li> <b>CVS folder appearing:</b> we have cases where the CVS folders |
| are appearing. This can happen if someone uses an external CVS client |
| then refreshes in Eclipse and our plugin isn't loaded. However, it |
| seems there are other cases. |
| <ul> |
| <li>Issue: we currently rely on pre-build delta notification to |
| mark the resources are team-private but this puts us in a race |
| condition with other listeners.</li> |
| <li>Issue: once a resource is known to the views, marking it as |
| team-private doesn't remove it since there is no delta.</li> |
| </ul> |
| <br/> |
| <b>Status:</b> We have done all we can without delta notification |
| support. There is an org.eclipse.team.cvs.delta plugin available <a href="dev.html">here</a> |
| that loads on startup and marks CVS folders as hidden. We are investigating |
| the possibility of obtaining the required delta notification support. |
| </li> |
| <p/> |
| <li> <b>Config maps:</b> there has been interest from the community |
| here, and one group who are willing to contribute the work to Eclipse. |
| <br/> |
| <br/> |
| <b>Status:</b> We have received a contribution from the community |
| in this area. Will need to investigate how to best make this available. |
| </li> |
| <p/> |
| <li> <b>Performance:</b> some operations can probably still be improved. |
| Decorators can be improved a bit. <br/> |
| <br/> |
| <b>Status:</b> Here is a list of specific performance improvements: |
| <ul> |
| <li>Use of lightweight decorators. |
| <li>Reduced memory usage by CVS plugin. |
| <li>Reduce startup time (<b>still to be completed</b>) |
| <li>Several localized optimizations. |
| </ul> |
| </li> |
| <p/> |
| <li> <b>Better modules support:</b> <br/> |
| <br/> |
| <b>Status:</b> Several improvements related to support of CVS modules |
| have been added. |
| <ul> |
| <li>"Checkout Into..." can be used from the CVS Repositories view |
| to check out a folder into an existing project.</li> |
| <li>Folders, such as those loaded using "Checkout Into...", can |
| be disconnected from CVS control from the folder's CVS properties |
| page, allowing the folder to be removed from a local project without |
| resulting in outgoing deletions.</li> |
| <li>A project shared with CVS can now be configured to not fetch |
| absent directories on update (i.e. previously, "cvs update" was |
| always performed with "-d". Now a project can be configured to |
| perform updates without "-d"). |
| </ul> |
| </li> |
| <p/> |
| <li> <b>Repository view:</b> current one is barely useful <br/> |
| <br/> |
| <b>Status:</b> Without changing the organization of the view, we have |
| added some improvements. For instance, the view supports working sets |
| and only shows projects under a branch that are known to be in the |
| branch. </li> |
| <p/> |
| <li> <b>CVS working sets - queries (investigate)</b>: we are interested |
| in being able to create working sets for CVS usage, eg. to show all |
| the dirty resources. We haven't thought this through far. The 2.1 |
| work item is to investigate this. <br/> |
| <br/> |
| <b>Status:</b> The working sets provided by the workbench are inappropriate |
| for this use. A new mechanism that would be able to filter the resources |
| in a view by criteria provided by other plugins is required. </li> |
| </ol> |
| <p><b>Items that may be 2.1 or 3.0</b></p> |
| <ol> |
| <li> <b>Useability:</b> some CVS dialogs and wizards, for example the |
| Tag Configution dialog and Set Keyword Mode Wizard, whose usability |
| could be improved. We'll try to do what we can in 2.1 but most work |
| will probably be done in 3.0. <br/> |
| <br/> |
| <b>Status:</b> Not addressed in 2.1 </li> |
| <p/> |
| <li> <b>Sync info and dirty decorators:</b> We discussed this in 2.0 |
| but didn't go forward with it. The problem is that to determine if |
| a project is dirty we must read in the sync info for every subfolder. |
| This is expensive, defeats late caching of sync info, and doesn't |
| scale for large projects or slow drives (e.g. network drives). <br/> |
| <br/> |
| <b>Status:</b> A cache was added to improve dirty foilder and file |
| determination </li> |
| <p/> |
| <li> <b>Watch/Edit:</b> we will proceed on this for 2.1 if we have community |
| involvement (we are not familiar with the usual workflows so have |
| asked for community guidance). Otherwise its 3.0. <br/> |
| <br/> |
| <b>Status:</b> Low-level support for this was added along with Team>Edit |
| and Team>Unedit menu items. Further work is being contributed by the |
| community. </li> |
| </ol> |
| <p><b>3.0 Items</b></p> |
| <ol> |
| <li> <b>Split the sync view:</b> We've talked about splitting it up |
| so that the sync part is a view, the edit area is an editor, and the |
| resource outline is an outliner view. </li> |
| <p/> |
| <li> <b>End-user customization of CVS strings:</b> This refers to the |
| strings we receive from the server and match against to determine |
| what is going on. Sometimes CVS users will customize their CVS server |
| and this can change the messages it sends us. Our pattern matching |
| then fails. Usually the changes are innocuous (ie. the semantics are |
| the same, we just fail the string matching). Idea is to externalize |
| these so clients can customize them to match their server. This assumes |
| that all required customization can be achieved against regular expression |
| patterns - we don't have enough experience with server customization |
| to know if this is sufficient. </li> |
| </ol></td> |
| </tr> |
| </tbody> |
| </table> |
| |
| </body> |
| </html> |
