incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
Date Mon, 13 Aug 2012 23:09:23 GMT



On 8/13/12 4:04 PM, "Carlos Rovira" <carlos.rovira@codeoscopic.com> wrote:

> Right! for that reason I said the new planed cases was something never came
> to flex before because all work was mainly "additive".
> 
> If you plan to make a new component...you can make it in develop, because
> it will not break nothing! since is new and nobody is using it.
> 
> Now thing in change UIComponent...it's clear that you can't make it in
> "develop" or you will generate a great problem once your first commit is
> done.
> 
> Consider the following... if the road to Flex 5 will be 30% additive and
> 70% modification of core flex components...what will you choose? (i'm
> setting percents only as a staring point, do not read as if it was true).
>
OK, but even modifications can be done without branching, right?  The key is
not to check things into "develop" that breaks things.

Other than Git handles branching better, the technical/logistical reasons
for branching are the same in all SCMs, correct?

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Mime
View raw message