You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David H. DeWolf" <dd...@apache.org> on 2005/03/24 15:26:54 UTC
Closing Issues (was Re: [jira] Commented: (PLUTO-109) )
Great question!
I've been resolving issues and leaving them for closure by the person
that submitted the bug. Unfortunately in most cases that never happens.
Once in a while, I'll close an issue directly if I resolve it as
invalid or won't fix.
What should our approach be?
David
CDoremus@hannaford.com wrote:
>
> Thanks, Carsten. I changed PLUTO-109 to Resolved. What is the criteria
> for moving a Jira issue to the Closed state?
> /Craig
>
>
>
> *Carsten Ziegeler <cz...@apache.org>*
>
> 03/24/2005 07:45 AM
> Please respond to
> pluto-dev@portals.apache.org
>
>
>
> To
> pluto-dev@portals.apache.org
> cc
>
> Subject
> Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch
> automatically $CATALINA_HOME/conf/server.xml to enable Application
> Scoped session attributes.
>
>
>
>
>
>
>
>
> Craig Doremus wrote:
> > Hi Carsten:
> >
> > I didn't realize I had two accounts. To get into Jira I use the user
> > name cdoremus; my email for that account is craig@maine.com. I hope
> > that's what you need.
> >
> Hi Craig,
>
> you are also registered under the user craig@maine.com (with the same
> email). I just added the user cdoremus to the Pluto project, so you
> should now be able to change issues.
>
> Should I delete the other user (craig@maine.com)?
>
> Carsten
>
> --
> Carsten Ziegeler - Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.org/weblogs/rael/
>
Re: Closing Issues (was Re: [jira] Commented: (PLUTO-109) )
Posted by Carsten Ziegeler <cz...@apache.org>.
David H. DeWolf wrote:
> Great question!
>
> I've been resolving issues and leaving them for closure by the person
> that submitted the bug. Unfortunately in most cases that never happens.
> Once in a while, I'll close an issue directly if I resolve it as
> invalid or won't fix.
>
> What should our approach be?
>
I think this is the usual way: you first set the issue to fixed and ask
the reporter to cross check and then close the bug. If after a period of
time, the reporter does not respond, we can imho close the bug then. But
we should give the reporter time to test.
In the case of invalid/won't fix I agree that they can be closed very
quickly - if the reporter has a different opinion he can reopen the bug
anyway.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/