Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 13 Feb 2006 13:36:18 -0800
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: Wiki for patches
In-reply-to: <8B4631EC-820E-445D-829E-ABA21E897469@gmail.com>
To: derby-dev@db.apache.org
Message-id: <43F0FBD2.5090906@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
References: <43F0DD73.5040906@sun.com> <43F0E437.7050803@sbcglobal.net>
 <43F0F4B0.3020006@sun.com> <8B4631EC-820E-445D-829E-ABA21E897469@gmail.com>

Thanks, Andrew. I will look for this box again later when JIRA isn't 
having an artistic fit.

Cheers,
-Rick


Andrew McIntyre wrote:

>
> On Feb 13, 2006, at 1:05 PM, Rick Hillegas wrote:
>
>> I'm afraid I'm more blind. Where on what screen is the "patch  
>> available" box?
>
>
> When you create or edit an issue, it's just below the description and  
> just above where you comment. It's small and unassuming - it doesn't  
> blink and it's not bright magenta - so it's easy to miss.
>
> When searching for issues, you pick Find Issues, and then you need to  
> select Derby as the project to search. That makes the custom 'patch  
> available' field appear in the bottom left section of the screen, in  
> the section labeled Custom Fields.
>
> Now that I've got the hang of the custom fields in JIRA, I could add  
> all sorts of things - drop-down boxes, radio buttons, checkboxes.  
> But, I don't want to overload JIRA with a bunch of fields whose state  
> is poorly maintained, either. A query for open issues with a patch  
> available should satisfy the answer to the question: what needs  
> review? That leaves the question: what needs commit? But, if there's  
> a checkbox for 'Patch needs commit,' but it will still be up to the  
> committer to review the review comments (be they in JIRA or on the  
> list) and determine whether or not there is consensus to apply a  
> patch, and the committer will still need to review the patch  
> themselves anyway, so I guess I'm just not sure what value another  
> checkbox would add.
>
> andrew