Re: SVN and issues with branching / consider how we use SVN going forward

[Alex Harui]

On 8/8/12 11:36 AM, "labri...@digitalprimates.net"
<labri...@digitalprimates.net> wrote:

> 
> The one nice thing about the release and feature branches is that it allows
> people to start working toward future releases and grand visions while a
> current release is being stabilized. For example the code many had in
> whiteboards that was destined for future releases.
> 
> Mike
> 
The author of the article seemed to want to make a release branch so that
whatever hits the trunk is essentially a snapshot of a release.  I'm not
quite sure that is worth it if at the point there is a group of us dedicated
to making a release and fixing things that are broken.  I wasn't thinking
we'd need to restrict checkins to unstable around release time if we are
being selective about what changes get promoted to trunk.  But if that
doesn't work out, then we would probably need to have release branches.

Feature branches are certainly ok in anyone's whiteboard or in branches, but
I don't know if we need policy around it.

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