Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD03AEA73 for ; Mon, 18 Mar 2013 09:18:05 +0000 (UTC) Received: (qmail 22165 invoked by uid 500); 18 Mar 2013 09:18:04 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 22130 invoked by uid 500); 18 Mar 2013 09:18:04 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 22117 invoked by uid 99); 18 Mar 2013 09:18:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 09:18:04 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of webdoublefx@hotmail.com designates 157.55.2.78 as permitted sender) Received: from [157.55.2.78] (HELO dub0-omc4-s3.dub0.hotmail.com) (157.55.2.78) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 09:17:58 +0000 Received: from DUB118-DS14 ([157.55.2.72]) by dub0-omc4-s3.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Mar 2013 02:17:37 -0700 X-EIP: [7VHN5Cfp4wD07FRsBagqSJnCLcYtaK/q] X-Originating-Email: [webdoublefx@hotmail.com] Message-ID: From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= To: References: <51945DCA-88BD-4375-BA5A-D22A1C09192A@classsoftware.com> <1A7A4DAC-9F43-4142-934A-FE6D99314F69@classsoftware.com> <3ADECCBE-36E1-40CD-B33E-4715B23F957E@classsoftware.com> In-Reply-To: Subject: Re: Git and revision numbers Date: Mon, 18 Mar 2013 10:17:33 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-OriginalArrivalTime: 18 Mar 2013 09:17:37.0572 (UTC) FILETIME=[6ED55640:01CE23B9] X-Virus-Checked: Checked by ClamAV on apache.org JIRA use the JIRA Fisheye plugin to link the sources with, aparently, it's not setup for our project, I retreived the infra ticket [1], we can then directly deal with altassian to setup our project with fisheye. >From [2] : Support FAQ Can we use Fisheye to browse and search our repository? Yes. See http://fisheye6.atlassian.com/ for some working examples. (Our Jira Fisheye currently disabled, looking into it) The people at Atlassian kindly provide FishEye instances of ASF projects, upon request. First, check with your project's PMC, and then ask Atlassian to setup a FishEye instance for your project. (No need to keep infra the loop.) Create a support request at Atlassian Support in the FishEye project. Please use the "Public Hosting" component for your request. If there is no response after a reasonable amount of time, infra has access to set up projects on Fisheye, but consider this a last resort option, Atlassian should be first point of contact. Atlassian now run a local synced copy of the ASF repository, hence requests can now be made direct without infra needing to be involved. So, I decided to open an issue at Altassian fisheye [3] -Fred [1] https://issues.apache.org/jira/browse/INFRA-5635 [2] https://cwiki.apache.org/INFRA/infra-faq.html [3] https://support.atlassian.com/browse/JST-59433 -----Message d'origine----- From: Fr�d�ric THOMAS Sent: Monday, March 18, 2013 9:29 AM To: dev@flex.apache.org Subject: Re: Git and revision numbers Who is JIRA admin btw ? it seem the fisheye plugin is there but misconfigured. -Fred -----Message d'origine----- From: Fr�d�ric THOMAS Sent: Monday, March 18, 2013 9:19 AM To: dev@flex.apache.org Subject: Re: Git and revision numbers > That's a feature we have but maybe broken (we should deal with infra IMO). -Fred -----Message d'origine----- From: Justin Mclean Sent: Monday, March 18, 2013 8:58 AM To: dev@flex.apache.org Subject: Re: Git and revision numbers Hi, > You can check writing the JIRA ticket id in the commit message(s), push > it/them , then go to JIRA, in the source tab, you should see all the > modified files (if this feature is not broken again). As far as I know this is not a feature we have - so what can we put in JIRA to show exactly what changes that have occurred. Justin