hi Ben, On Thu, Apr 23, 2009 at 10:36 PM, Ben Dewey <[email protected]> wrote:
> Where would a committer look for patches that haven't been committed? > > > Should I resolve the issue when the patch has been attached? You should not resolve the issue when attaching patch. It should be resolved only after applying patch. This will answer your first question as well. So a committer will find unapplied patches from unresolved issues. Normally they will not check any resolved issue (Specially, down the line, we will have 100s of resolved issues, so no way checking them :-) ) Regards, Shankar. > > > -Ben > > > -----Original Message----- > From: Drew Baird (Volt) [mailto:[email protected]] > Sent: Thursday, April 23, 2009 1:04 PM > To: [email protected] > Subject: RE: Resolved - > Closed > > Any committer can pick up and test/commit a patch. I just happen to be > working the dotnet side. > Hopefully Shankar will pick up the WSAS patch since I am not there yet. > > Try to close and let's see what happens. > > Drew > > -----Original Message----- > From: Ben Dewey [mailto:[email protected]] > Sent: Thursday, April 23, 2009 9:51 AM > To: '[email protected]' > Subject: RE: Resolved - > Closed > > So, > > For a Non-Committer. Should I resolve the issue when I attached the patch > file. Then when the patch has been committed and verified I should go back > in and Close the issue? > > Also should I be asking a committer to apply the patch, (I've been asking > Drew)? Or should I just wait till someone goes thru and picks-up the > resolved patches to commits them? What the procedure here? > > -Ben > > > > -----Original Message----- > From: Dimuthu Gamage [mailto:[email protected]] > Sent: Wednesday, April 22, 2009 9:50 PM > To: [email protected] > Subject: Re: Resolved - > Closed > > Hi Drew, > I think it is really close to what you guessed. Here is how it goes as I > have heard and seen, > > 1. Anybody (it can be a commiter or a non-commiter) can report a JIRA. > 2. Commiters can assign a jira to himself and resolve them. (Non-commiters > should apply patches, they can't directly assign or resolve jiras) > 3. Normally the one who reported the jira should verify the fix and close > it > or reopen if it is not fixed. Even a non-commiter can close a JIRA reported > by himself. > 4. If the one who reported the jira is not closing it for a long time, a > commiter can close it. Normally this is done near a release. > > > On Thu, Apr 23, 2009 at 6:00 AM, Drew Baird (Volt) > <[email protected]>wrote: > > > Hi all, > > > > What is the Apache Best Practice for resolving and closing Jira issues? > > > > I would think the developer would mark it resolved when he is finished > and > > then 'someone else" would close the issue after it has been verified. > > > > Comments from the the mentors would be appreaciated. > > > > Thanks! > > Drew > > > > > > > -- > Thanks, > Dimuthu Gamage > > http://www.dimuthu.org > http://www.wso2.org > > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
