On 8/13/12 3:45 PM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> wrote:
> Hi Alex,
>
> 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 first?
>> 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?
>>
>>
> First considere that in Git, "develop" use to be as stable as possible and
> you can make nightly builds from this branch and "master" use to be
> production ready with the release we made.
>
> Normaly, if you are working in a set of spark charts, your work will spawn
> over some weeks. So if you work directly on develop, you should not commit
> 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 would
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.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
