flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
Date Mon, 13 Aug 2012 23:21:03 GMT
> 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, that's ok, and is up to you to take that kind of decission. It's like
to make to make a huge flex/java ERP with notepad. It can be done, but it
will very hard in the day-by-day basis. Better to choose directly the
better IDE to go as fast as possible.

Here's the same, you hardly will go the way to refactor UIComponent all
alone and not commit until work is done, because, you know, although that's
possible, it's highly improbable and you will need in some step to share
and test with other people, discuss code and so on.

One thing different in Apache from the work done in Adobe until this
release is that Flex 2.x, 3.x and 4.x was done internaly and only released
when the overall plan was complete. Now the playground is different and
people can share (commit in SVN) some unfinished work and then let the
trunk unstable until other people takes over this work to fix it.

This seems for me an horrible scenario and Git could avoid that because
PPMC will be pushing only stable features into develop from all pull
request ensuring "develop" and then "master" are always stable.

Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message