We could also use status "closed" with resolution "fixed" which should be
changed to "accepted" after when the release is published.
--DimitriPolivaev<http://freemind.sourceforge.net/wiki/index.php?title=User:DimitriPolivaev&action=edit>04:06,
14 Jul 2007 (PDT) That solves the con 1. What about the con 3? Anyway,
setting to closed
issues that are in some beta version, not with the last stable version,
seems fine to me. Whoever downloaded one beta is probably willing to
download another beta or RC. But these issues would be set to solved only
after another beta or RC is published. All right? So the only items now in
discussion are bugs and requests in the last stable version that have been
solved in CVS. What about them? Setting them to closed would still cause
that people would not see them in the tracker.
--Danielpolansky<http://freemind.sourceforge.net/wiki/index.php/User:Danielpolansky>04:20,
14 Jul 2007 (PDT)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Freemind-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freemind-developer
