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). Now if we are considering only add new components ad infinitum letting flex as is, I will not loss any more time trying to argument why Git is the option, and will not be worried for the SCM to choose, because it will not be decisive in the long time. Git ritght now is decisive in the short and in the long time... 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 > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
