flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: SVN and issues with branching / consider how we use SVN going forward
Date Tue, 07 Aug 2012 22:46:21 GMT

On 8/7/12 9:02 AM, "Bertrand Delacretaz" <bdelacretaz@apache.org> wrote:

> On Tue, Aug 7, 2012 at 5:52 PM, Carol Frampton <cframpto@adobe.com> wrote:
>> ...if you are working on a feature that will take you
>> some time to complete (or more than a release cycle) and you can't break
>> it down into useable sub-pieces, and you want to check in at intermediate
>> points, the code needs to go somewhere other than trunk....
> IMO the key is "can't break it into useable sub-pieces" - that's
> usually a sign of something being wrong at the design level, which
> might happen from time to time but shouldn't be the rule.
> I often take the extreme modularity of httpd.apache.org as an example
> to follow: making things more modular allows people to work in
> parallel without stepping on each other's toes, and also dramatically
> reduces the amount of coordination that's needed to work efficiently.
> Maybe Flex needs a bit of that to make it easier to collaborate - I
> don't know the codebase enough to comment on that.
> -Bertrand
Unfortunately, Flex isn't as modular as it should be.  And given that I
don't think we have enough tests to keep trunk in good shape, I'd lean
towards playing it safe with an unstable branch until we can prove that we
can keep it in shape.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message