Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of omarg.developer@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <EB6F7A48D477254EAB8F675582F80CD7267CFEE4@DPSBS1.digitalprimates.local>
References: 
 <EB6F7A48D477254EAB8F675582F80CD7267CFB18@DPSBS1.digitalprimates.local>
	<CC47E77A.4425C%aharui@adobe.com>
	<EB6F7A48D477254EAB8F675582F80CD7267CFEE4@DPSBS1.digitalprimates.local>
Date: Wed, 8 Aug 2012 18:45:52 -0700
Message-ID: 
 <CAEFz_vsSMjOGroKJ6_HRX7_uZQiDN8-ksuq_SYfWRXSBCkhN4A@mail.gmail.com>
Subject: Re: SVN and issues with branching / consider how we use SVN going
 forward
From: Omar Gonzalez <omarg.developer@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf307abeed39ae8e04c6cb63ac

--20cf307abeed39ae8e04c6cb63ac
Content-Type: text/plain; charset=ISO-8859-1

>
> t saying it is worth it in order to protect the integrity of trunk.
>
> If it's possible, yes, I really do think Git would help. The reason is
> that dealing with merge issues in Git are infinitely easier and, at least
> 95% of the time, keeps us out of the merge-hell that I think Justin
> legitimately fears.
>
> The one nice thing about the release and feature branches is that it
> allows people to start working toward future releases and grand visions
> while a current release is being stabilized. For example the code many had
> in whiteboards that was destined for future releases.
>
> Mike
>
>
I agree with all of this. I would be completely in favor of making Git the
primary SCM for the project, it would really make a lot of these workflows
easier to manage amongst so many developers. I also posted about the link
Mike shared and that model has worked great for our teams.

-omar

--20cf307abeed39ae8e04c6cb63ac--