Re: closing invalid/won't fix jira issues
Yes, closing them immediately is what is was decided some time ago. Thus, we ease the burden of closing all the JIRA issues later... Regards, Bruno 2005/11/24, Martin Marinschek [EMAIL PROTECTED]: +1 for closing immediately. We can always reopen later ;). The last time I closed Thomas bugs, I'll talk to him to use close instead of resolve as well. regards, Martin On 11/23/05, Mike Kienenberger [EMAIL PROTECTED] wrote: Yeah, the other projects I've been on that use JIRA mark bugs closed after a public release is made. I did a quick search and only Thomas was marking things resolved but not closed, so I went ahead and closed it.Since the second report was submitted as an improvment, WON'T FIX is probably good enough, but I did strongly consider INVALID :) Thanks for commenting. On 11/23/05, Simon Kitching [EMAIL PROTECTED] wrote: Hi Mike, Mike Kienenberger wrote: Should I be closing invalid or won't fix jira issues at the same time I resolve them? I would personally have marked this particular issue invalid rather than wontfix. invalid: the report is not a bug. wontfix: it's agreed that it is a bug or misfeature but there is no intention of making any change. And as MyFaces doesn't have a QA dept to double-check resolved issues and mark them fixed, I think it's better to use closed immediately rather than resolved. But that's just my opinion. Cheers, Simon -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
closing invalid/won't fix jira issues
Should I be closing invalid or won't fix jira issues at the same time I resolve them?
Re: closing invalid/won't fix jira issues
Hi Mike, Mike Kienenberger wrote: Should I be closing invalid or won't fix jira issues at the same time I resolve them? I would personally have marked this particular issue invalid rather than wontfix. invalid: the report is not a bug. wontfix: it's agreed that it is a bug or misfeature but there is no intention of making any change. And as MyFaces doesn't have a QA dept to double-check resolved issues and mark them fixed, I think it's better to use closed immediately rather than resolved. But that's just my opinion. Cheers, Simon
Re: closing invalid/won't fix jira issues
Yeah, the other projects I've been on that use JIRA mark bugs closed after a public release is made. I did a quick search and only Thomas was marking things resolved but not closed, so I went ahead and closed it.Since the second report was submitted as an improvment, WON'T FIX is probably good enough, but I did strongly consider INVALID :) Thanks for commenting. On 11/23/05, Simon Kitching [EMAIL PROTECTED] wrote: Hi Mike, Mike Kienenberger wrote: Should I be closing invalid or won't fix jira issues at the same time I resolve them? I would personally have marked this particular issue invalid rather than wontfix. invalid: the report is not a bug. wontfix: it's agreed that it is a bug or misfeature but there is no intention of making any change. And as MyFaces doesn't have a QA dept to double-check resolved issues and mark them fixed, I think it's better to use closed immediately rather than resolved. But that's just my opinion. Cheers, Simon
Re: closing invalid/won't fix jira issues
+1 for closing immediately. We can always reopen later ;). The last time I closed Thomas bugs, I'll talk to him to use close instead of resolve as well. regards, Martin On 11/23/05, Mike Kienenberger [EMAIL PROTECTED] wrote: Yeah, the other projects I've been on that use JIRA mark bugs closed after a public release is made. I did a quick search and only Thomas was marking things resolved but not closed, so I went ahead and closed it.Since the second report was submitted as an improvment, WON'T FIX is probably good enough, but I did strongly consider INVALID :) Thanks for commenting. On 11/23/05, Simon Kitching [EMAIL PROTECTED] wrote: Hi Mike, Mike Kienenberger wrote: Should I be closing invalid or won't fix jira issues at the same time I resolve them? I would personally have marked this particular issue invalid rather than wontfix. invalid: the report is not a bug. wontfix: it's agreed that it is a bug or misfeature but there is no intention of making any change. And as MyFaces doesn't have a QA dept to double-check resolved issues and mark them fixed, I think it's better to use closed immediately rather than resolved. But that's just my opinion. Cheers, Simon -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
