In XMLBeans project, Y fixes, resolves the isue and assigns to X for checking and closing. If X doesn't close it for a while (usually more than several months) than Y or any commiter can close it. If X is not satisfied he can always reopen the issue.
Cezar On Tue, Nov 17, 2009 at 8:23 AM, Till Westmann <[email protected]> wrote: > I would guess that the Apache answer to that question is: "The project > decides". 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. > > Till > > -------- Original-Nachricht -------- > > Datum: Mon, 16 Nov 2009 19:23:51 -0800 > > Von: Vinayak Borkar <[email protected]> > > An: [email protected] > > Betreff: Resolved Issues in JIRA > > > Guys, > > > > > > What is the usual lifecycle of issues in Apache projects? > > We have a bunch of issues marked "Resolved" in JIRA. Can I go ahead and > > close them? > > > > In general, lets say X reports a bug and assigns it to Y. Y fixes the > > issue, does Y mark it as resolved? > > > > Is the assignee changed to X, so they get a chance to try the issue out > > and close it if it is indeed fixed? Or can the developer (Y in this > > case) can go ahead and do that unilaterally? > > > > Thanks, > > Vinayak >
