From dev-return-19058-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Tue Nov 01 22:54:06 2005 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 81506 invoked from network); 1 Nov 2005 22:54:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Nov 2005 22:54:05 -0000 Received: (qmail 57983 invoked by uid 500); 1 Nov 2005 22:54:04 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 57293 invoked by uid 500); 1 Nov 2005 22:54:03 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 57282 invoked by uid 99); 1 Nov 2005 22:54:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 14:54:02 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [199.237.51.194] (HELO green.rootmode.com) (199.237.51.194) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 14:53:58 -0800 X-ClientAddr: 68.171.62.46 Received: from [192.168.15.100] (68-171-62-46.vnnyca.adelphia.net [68.171.62.46]) by green.rootmode.com (8.12.10/8.12.10) with ESMTP id jA1MrXUh007093 for ; Tue, 1 Nov 2005 17:53:34 -0500 Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <4367EE0E.20305@earthlink.net> References: <4367E660.6090300@earthlink.net> <9e3862d80511011409q3ecb4753xdd8d3b9c5173321f@mail.gmail.com> <4367EE0E.20305@earthlink.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <31C602C7-4D60-4BFD-BC8A-3B3D1118E9CD@iq80.com> Content-Transfer-Encoding: 7bit From: Dain Sundstrom Subject: Re: How to identify a JIRA with a patch. Date: Tue, 1 Nov 2005 14:53:36 -0800 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.734) X-RootMode-MailScanner-Information: Please contact the ISP for more information X-RootMode-MailScanner: Found to be clean X-MailScanner-From: dain@iq80.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Done. Geronimo and Geronimo-dev issues now have a custom "Patch" field at the bottom of the issue. Here is a report: http://issues.apache.org/jira/secure/IssueNavigator.jspa? mode=hide&requestId=12310367 Now I'll try to figure out the security issue raised by brett. -dain On Nov 1, 2005, at 2:37 PM, Joe Bohn wrote: > > I like this suggestion for when you only want to pull up a list of > JIRAs that have patches attached (very creative). > > One of the other things I was hoping to use this for was to look at > a release, component, whatever .... and see how many potential > fixes we already had and how many are still "untouched". It would > also be a good way for non-committers to see what items are open > and waiting for attention. We could do the inverse of the "patch" > search but it would be nice to see both types in one view with some > differentiation. > > Joe > > > Brett Porter wrote: > >> Not as far as I know. I'm tracking a JIRA ticket at Atlassian for the >> ability to detect the existence of an attachment, but that stiff >> doen't designate if its a patch unfortunately. >> In our project we just query for "patch" in any of the text >> fields. We >> generally find that people type that somewhere when attaching it. >> - Brett >> On 11/2/05, Joe Bohn wrote: >> >>> Is there any way to get a view of JIRAs that have files(patches) >>> attached? >>> >>> If not, can we begin some kind of convention? I noticed that >>> some folks >>> have added (Patch) to the start of the title for a few JIRAs. Do >>> you >>> think that would be helpful? >>> >>> I image it must be a pain for the committers to get a view of the >>> available patches. >>> >>> Any other suggestions? Anybody how other projects manage this? >>> >>> Joe >>> >