An issue is typically marked as Resolved after the patch is applied, unit tests passed, and the modified code is committed to the repository.
In enterprise environments the issue is typically closed after it's been verified by the QA. In case of an open-source project there may be no need for separation of Resolved and Closed. In Lucene land we just mark bugs and patches as Resolved/Fixed and don't bother with closing them. Otis --- Stefan Groschupf <[EMAIL PROTECTED]> wrote: > Hi, > I'm confused by this comment: > Doug: "In the future, things shouldn't be resolved until the patch > is > committed. I just committed this." > http://issues.apache.org/jira/browse/NUTCH-29#action_61664 > > I personal understand the life cycle of a issue like this: > > - Create an issue. > - Assign an issue to a developer (optional) > - Resolve a issue as soon someone start to work on this issue > - Close the issue as soon the patch is in the sources > > Do people see it different? When should issues closed and when > resolved? > > Stefan ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
