On Nov 17, 2009, at 10:39 PM, Vinayak Borkar wrote: >>> If so, I'd propose that the reporter verifies the resolution and closes the >>> issue. >>> However, I also would like to know how other projects handle this. >> Totally different. For example, in XML-RPC, we leave the issues >> "resolved" until we publish a new release, in which case we use the >> "resolved" issues to create a report and close them. >> Jochen > > What if we do the following? > 1. Fix the issue, mark it as resolved, and assign it to the original issue > creator. The issue creator has the opportunity to reopen it or add a comment > that it is indeed fixed. > 2. We leave resolved issues as "resolved" until release time. We create > ChangeLog entried from the resolved issues and close them.
Sounds good to me. May we can close some issues that are not really relevant for the deliverable (like "set up mailing lists") earlier, but everything should be closed by the time we release. Till
