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 222EA108D5 for ; Thu, 5 Sep 2013 02:28:53 +0000 (UTC) Received: (qmail 60065 invoked by uid 500); 5 Sep 2013 02:28:52 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 60035 invoked by uid 500); 5 Sep 2013 02:28:52 -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 60026 invoked by uid 99); 5 Sep 2013 02:28:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 02:28:52 +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.106 as permitted sender) Received: from [157.55.2.106] (HELO dub0-omc4-s31.dub0.hotmail.com) (157.55.2.106) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 02:28:45 +0000 Received: from DUB402-EAS62 ([157.55.2.71]) by dub0-omc4-s31.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 4 Sep 2013 19:28:22 -0700 X-TMN: [Ljvx+o/HCvv0yPAx0QaFTUfpdshFB/Bb] X-Originating-Email: [webdoublefx@hotmail.com] Message-ID: From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= To: References: <60A76408-40A3-48AD-96A2-FD48FAF04253@classsoftware.com> <12FA9C60-61FC-44F9-8AF2-2228F6CB3A8C@classsoftware.com> <7E4B0D6F-39E0-4BB4-8D68-B994398E4979@classsoftware.com> In-Reply-To: Subject: RE: Nighly builds and releases Date: Thu, 5 Sep 2013 04:27:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 thread-index: AQABAgMEbytuZknwH3D0vuEx2dAXfgCtqCObAI0pQ50AQDszqACPMH9kAIkmiAYAblKprABME8BJAFPilMEAiYESrwDV+gTwACKQl+sA8rY8EgAU23kcAA5pdoIA4M8GcgBuKQTpAIr75pqdERnroA== Content-Language: fr X-OriginalArrivalTime: 05 Sep 2013 02:28:22.0440 (UTC) FILETIME=[9778CA80:01CEA9DF] X-Virus-Checked: Checked by ClamAV on apache.org > How do you merge back into develop easily? That's here there is something I don't know, what should be merged back = to the develop branch ? We haven't got hotfixes and if something goes wrong with the RC, it is = fixed on the dev branch and another RC is done, right ? Even if we would fix on the RC, only this fix should be merged back or = I'm wrong ? What else ? -Fred -----Message d'origine----- De=A0: Justin Mclean [mailto:justin@classsoftware.com]=20 Envoy=E9=A0: jeudi 5 septembre 2013 04:05 =C0=A0: dev@flex.apache.org Objet=A0: Re: Nighly builds and releases HI, > What was the problem exactly ? One of the RCs had a build number of 0. The file in question was in gitignore so the difference wasn't picked up until a RC had been made = and several people had tested it. > why attributing a build number only at release time would make it = harder How do you merge back into develop easily? Isn't it simpler not to have exceptions, rather than say merge all files except these ones. The = release process is complex enough as it is and we're had zero people other than = me to step forward to do a release (past the initial 4.8 one) because of = that. Thanks, Justin