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 A1342E578 for ; Mon, 18 Mar 2013 20:55:12 +0000 (UTC) Received: (qmail 38561 invoked by uid 500); 18 Mar 2013 20:55:11 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 38535 invoked by uid 500); 18 Mar 2013 20:55:11 -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 38527 invoked by uid 99); 18 Mar 2013 20:55:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 20:55:11 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 20:55:07 +0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so3493982wib.3 for ; Mon, 18 Mar 2013 13:54:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type:content-transfer-encoding :content-disposition:x-gm-message-state; bh=9omAZ3Nkmhfa1FXOsbYKoYKP5XqYFM4zb1OYxERGHfA=; b=JfcSLtB6GXx+OAaqPOEo3rEtGD00cEyP4VFDxsdIe1Z8VLH0Nl2aYTH1JhAKdVkQSh MY6IU+9Gk79wW/lqm6LVpLZtAHVcidv4BhxMMWtoLb2C9FjOtRKQCcRBlsMa89+DnSMP /T2Hi9H01u07qWRbhaBf/5rrydLo7BxBLHmltLw1IMovvrlomGb0G2yGMrD6DiLxN5sA K5i4DgjcT4SI+IZkGEGFaRx9PPRcnVLJW1x33QEHqYob7RGp1F03ANMiDUunInvi964O XhGoWKKNmG1xpfOwtPhKEGBBGXb+nvAGO84g+FoUQsQd4dnyFHFsrtHm9dPelTgxmXzm NR7g== X-Received: by 10.180.105.229 with SMTP id gp5mr876563wib.10.1363640085545; Mon, 18 Mar 2013 13:54:45 -0700 (PDT) Received: from [192.168.0.6] (D57E16C2.static.ziggozakelijk.nl. [213.126.22.194]) by mx.google.com with ESMTPS id k5sm17345867wiy.5.2013.03.18.13.54.43 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 18 Mar 2013 13:54:44 -0700 (PDT) Date: Mon, 18 Mar 2013 21:54:43 +0100 From: Erik de Bruin To: dev@flex.apache.org Message-ID: <4B4001A7A2B74F07AF1042822493629D@ixsoftware.nl> In-Reply-To: <149F8129B58B2D418508E63117D9C5419BDE675544@nambx05.corp.adobe.com> References: <330AAE2D996842FB96372A3A40ACC281@ixsoftware.nl> <149F8129B58B2D418508E63117D9C5419BDE675544@nambx05.corp.adobe.com> Subject: Re: nvie branch model X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Gm-Message-State: ALoCoQkuimYr7pcOH1eoAA+Mk4LKYH25dsuBzryqiR3YLLJI7KeICJnaPEzWezjoYC9hmolbjzif X-Virus-Checked: Checked by ClamAV on apache.org Gordon, Yes, to me this seems like the way to go. We work in 'develop' and once we think we're ready for 1.0, we cut a release branch, make that work and once done merge all of that into 'master' and tag it 1.0. Until then, we ignore 'master' ;-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl (http://www.ixsoftware.nl) On Monday, March 18, 2013 at 21:25, Gordon Smith wrote: > Erik, are you OK with just doing everything on a 'develop' branch? > > - Gordon > > -----Original Message----- > From: Erik de Bruin [mailto:erik@ixsoftware.nl] > Sent: Monday, March 18, 2013 1:16 PM > To: dev@flex.apache.org (mailto:dev@flex.apache.org) > Subject: Re: nvie branch model > > I don't agree with that. I think we need 'develop' if for nothing else that set us up correctly from the start. Not sure about Mike, but you, Gordon and me are all absolute beginners on git, and following the agreed upon procedures (nvie.com (http://nvie.com)) will make it easier to get help from the proponents and attract contributors. > > > EdB > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl (http://www.ixsoftware.nl) > > > > On Monday, March 18, 2013 at 21:12, Alex Harui wrote: > > > > > > > > > On 3/18/13 12:54 PM, "Gordon Smith" wrote: > > > > > My understanding is that we've decided to follow > > > > > > http://nvie.com/posts/a-successful-git-branching-model/ > > > > > > but the first diagram looks like spaghetti to me. There are > > > relatively few people working in the flex-falcon repo, and I'd like > > > to understand what we have to do to be minimally compliant with the > > > nvie model. Is it sufficient to simply create a 'develop' branch in > > > addition to 'master' and then do development there? Would we delay > > > merging to 'master' until we reach a 1.0 release? > > > > > > > > > > Yes, that is the minimum required. I'm ok waiting to do all of that > > until we actually cut a first Falcon release. > > > > -- > > Alex Harui > > Flex SDK Team > > Adobe Systems, Inc. > > http://blogs.adobe.com/aharui >