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 aharui@adobe.com designates
 64.18.1.191 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Mon, 13 Aug 2012 15:53:20 -0700
Subject: Re: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
Thread-Topic: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
Thread-Index: Ac15pVsF05nwg52ASLOV13bPadv3RwAARQiT
Message-ID: <CC4ED370.44705%aharui@adobe.com>
In-Reply-To: 
 <CAMFKFRjzzx9txnPPbiBR_e4iJZDxqakQRS1MO41ZsmAy==+e=A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


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

> Hi Alex,
>=20
> What is that "clarity"?  Can you give me an example?  If I want to
>> contribute a set of Spark Charts, why should I have to cut a branch firs=
t?
>> Why can't I just check in ChartBase into the "develop" branch, then add =
in
>> Pie, Bar, etc over time in subsequent check ins as I finish them up?
>>=20
>>=20
> First considere that in Git, "develop" use to be as stable as possible an=
d
> you can make nightly builds from this branch and "master" use to be
> production ready with the release we made.
>=20
> Normaly, if you are working in a set of spark charts, your work will spaw=
n
> over some weeks. So if you work directly on develop, you should not commi=
t
> your work to SVN until is done because you will make "develop" unstable
> until you close the feature.
Interesting, that's a different definition of "unstable" than I was
thinking.  One of the goals I think folks had was to get stuff out of their
whiteboards and into a shared working environment sooner so more folks woul=
d
notice it and it would get better faster.  Requiring everyone to work in
their own branches until "complete" seems overly restrictive.

IMO, if a new component is "working" (i.e. doesn't break any existing tests=
)
and is ready for other folks to use, it should be allowed into the "develop=
"
branch.  It doesn't have to be feature complete, bug-free or otherwise
production ready.

For sure, if you are doing a risky change to UIComponent then a branch is
wise.

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