flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Costa <igorco...@gmail.com>
Subject Re: [VOTE] Branching Strategy and SCM
Date Tue, 14 Aug 2012 02:11:00 GMT
Vote is the better political agreement between parts.

After 2 years we will look back into this thread and We will considering
change Flex Git project. other than SDK.

Come on, people, just Vote and take yours comments on old thread for it.

I'm with Carol, I will not support Git right now, unless Apache does
recognize as good for the projects.

On Mon, Aug 13, 2012 at 9:50 PM, Justin Mclean <justin@classsoftware.com>wrote:

> Hi,
> I think it's a little early to be taking a vote when there no clear
> consensus and some of the details of the branching models are a little
> unclear, but as a vote has been called for:
> +1 (binding) for option 4
>  My reasons include:
> - The apache git set up is still experimental. I'd be fine to work in Git
> when it's fully supported.
> - git-svn can be used now - not ideal (no pull requests) but means you can
> use Git if you want.
> - Option 4 is simple. Options 1-3 and 7-9 IMO add unnecessary complexity
> and go against best practice (ie cherry picking). Branches are fine, it's
> branches and cherry picking and then merging multiple branches is where you
> run into issues. I'm fairly certain that the gitflow branching model did
> not involve cherry picking so not sure how that has crept in.
> - Unsure how it is decided what from develop/trunk goes into a release.
> IMO this will make releases a lot more work for the release manager and
> less likely someone will want to take on that role.
> - Advice from mentors favours this option.
> Thanks,
> Justin

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