Hi, still cleaning up my inbox after my holiday.
We currently don't really use groups. I had created two of them aligned with FreeMind versions while I was doing some cleanup with the idea of assigning the group to a tracker entry means "this bug can still be found in version X". We could also create groups called "Solved after X" meaning "After release of version X, this bug has been fixed (in CVS or Subversion, whatever), it should be gone in the next version." i.e. a bug should either be in group "FreeMind X" i.e. it's in the current version and hasn't been fixed yet, or in group "Solved after X", and we know it's fixed. Bugs still open with no groups and in other groups can be tested against the latest version by less knowledgeable guys like me and put in the group "FreeMind X" for developers to solve. Pros: 1- users see by default all bugs they might find in the current version, even if they're fixed in CVS/Subversion, and we avoid duplicates. 2- developers can filter on group "FreeMind X" in order to see the bug they should concentrate upon. 3- before release, testers can filter on "Solved after X" to check that the bugs are really gone. 4- testers can also filter on "FreeMind Y" (Y<X) and check if the bug still exists in version X, close it if not, change group to "FreeMind X" if yes. Cons: 1- need to create 2 new groups for each release, and groups can't be deleted. We could alleviate this by creating groups only for stable releases; actually it's not a bad idea, I don't think it would hurt much anybody. 2- bugs closed because fixed in a released beta version are not seen anymore by users using a stable version. To fix this, we could decide to close only after release of stable versions. I personally think that it would be too messy. We should close after each release, and alleviate by releasing more often stable versions... Does it make sense? Eric Dan Polansky wrote: > Leaving items open until a solution is provided to the customer IS A > DEFINED PROCESS, which is not to say it is a good one. Did you think of > other options besides the one you have suggested? What about using other > fields for filtering, like Category or Group? Both are currently used > for other purposes, but that could be changed, depending what you > consider your priority when filtering. There surely are some other > solutions, possibly worse in some regard. It is just that I did not hear > any other so far. --Dan > > On 7/14/07, *Dimitry Polivaev* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > The important thing is that we have a solution which is better than > nothing. If one had a better one we could use it too, but currently we > do not have any solution and any policy. > > Leaving items open for an undefined period of time is not a way which > sounds like a defined and understood process, is it? > > Best regards, Dimitry. -- Gewalt ist die letzte Zuflucht der Inkompetenz. Violence is the Last Resort of the Incompetent. Gwalt jest ostatnem schronieniem niekompetencji. La violence est le dernier refuge de l'incompetence. ~ Isaac Asimov ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
