Sure! Until working we mark the issue as in progress and when the patch is committed we mark it as as resolved. So the only thing to discuss when we should close a bug.
Since we have no QA and no test group yet, what you think about we close bugs when releasing the next version?
Make that sense? I will take care of this process but need a rule to follow.


Stefan


Am 12.04.2005 um 20:06 schrieb Doug Cutting:

Stefan Groschupf wrote:
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

I'm used to not resolving them until they're fixed. See, e.g.:

http://issues.apache.org/bugzilla/page.cgi?id=fields.html#resolution

If you have a test group, then they're not closed until they've been verified, but, without a test group, we just close them as they're fixed.

Does Jira have different conventions?

Doug


---------------------------------------------------------------
company:                http://www.media-style.com
forum:          http://www.text-mining.org
blog:                   http://www.find23.net



-------------------------------------------------------
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

Reply via email to