Bugzilla – Full Text Bug Listing
| Summary: | [Change Sets] Task oriented sessions | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Xavier Méhaut <xavier.mehaut> |
| Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Xavier Méhaut
Furthermore, we could enhance the feature by adding requirement management ability. For each task defined, we could provide additional information about the content of the task, the nature of the requirement or use case , the category of the requirement, ... So we would have then the begiining of a development methodology integrated with eclipse best regards Xavier We are starting along this path with commit sets (soon to be changed to Change Sets). These will make a lot of the things you suggest possible. I do have some comments and questions about some of your statements: Statistics: This is not something I've though much about. What type of statistics do you think would be useful here? Unload and Reload: We could support and export/import task bu tthis would be little more that creating and applying a patch. What would make this compelling would be the ability to include binary files and the change set (task) information. Regarding your second comment, we are working on integration between the change set (tasks) and bug reporting tools. This seems related to what you are requesting here. Hi Michael, I'm glad to know that such features are ongoing; actually these features are already available in many tools under different views. For instance, in Clearcase we can have a task oriented view (not mandatory). In Issue management tools (like my own project elips - opinionplugin.sourceforge.net), we have tasks definitions abaility and time tracking too. Project planners add statistics on time tracking. Methodological tools add the ability to define requirements as "use case" for instance. If we look afetr these features we can see that they are all interconnected (strong coupling). As I imagine the overal process is the following : * ability to define "use cases" , ie requirements int Eclipse . It could be a Requirement view anebling to define requirements trees. If we looak at for instance C#, we see that the namespace notion could be seen (if it were possible to have several namspaces for a class for instance) as a grouing of elements participating to a requirement achievement. It is orthogonal to the package notion.It could be good to have in eclipse this kind of view, kind of filtering wrt to a given requirement * a use case must give then a task to achieve. So the user open a task (change set like in smalltalk) and close it at the end * associated to the task , we can have many information like the time spent, the number of element touched, metrics on the coupling between the elements involved in the task, and so on... We can have also a time summary for all the tasks of the user... * wrt to the coupling with bug/issue trackers, it could be good to have a generic interface between eclipse and the tools by using web services to pilot the tools. Concerning the load/unload feature, the patch fetaure is not satisfying up to now. The patch is a CVS readable output. Imagine for instance you have delivered a version of your application, for instance 1.5.0. You have several users who downloaded and tested the application and they find critical bugs. Normally you have to deliver a maintenance release for correcting the bug, but for this kind of pb you haven't the time to deliver it. You only have the time to deliver a patch. So the idea, is to open a "patch" task , make changes, and then export the changes into .zip file you can load on your delivery site. So now, another scenario ; you started to develop code for a specific task. You have coeed some material but you guess that the implementation is not effective or even wrong...It would be nice to unload the changes to rego to the previous state before stating the taks...and better to have the ability to indicate miletstones in the development of the task (like the recovery point in windows) and to be able to refind the chosen states. It was in a certain manner possible in smalltalk by quitting without saving the image. best regards Xavier Not for 3.1 *** Bug 107843 has been marked as a duplicate of this bug. *** Although this is a good idea, this type of tooling is outside the scope of the Team/CVS component. |