On 8/15/12 1:13 PM, "labri...@digitalprimates.net"
<labri...@digitalprimates.net> wrote:
>> Mike, there's about 2.5 hours left. If you change your vote to #9 and get a
>> few others who responded to the poll but did not vote to move to #9, you can
>> probably tip the scales in favor of GBM.
>
> Alex,
>
> How about you next? Wanna switch from Git later to Git now? We have people
> here who want to do the work. Shall we help them do so?
>
> Mike
>
My current count says it is 5 for Classic, 4 for GBM. If you can get one
more from someone else to tie it up, I will switch over to break the tie in
favor of GBM (unless the Classic folks also stage a rally).
I've been pondering the notion that it just seems too risky to move to Git
now and what we really need is for GBM to win. The fine print in the ballot
says that if #9 wins but Apache doesn't let us move to Git now, we would
implement GBM on SVN until Apache makes Git official (which AFAICT is a
matter of when, not if).
Given what I know we want to do short term, I think we can live with GBM on
SVN for now. The next release isn't going to contain any UIComponent
refactoring, we've got lots of mustella tests to fix and some new components
to integrate. I think SVN can handle that. If we implement GBM on SVN,
which pretty much means make a "develop" branch and having folks work there,
I think that allows committers to use Git and git-svn to commit and the
community to use our Git mirrors now. And hopefully infra will bless Git
read/write repos this year after our second release (and maybe even
graduation) and we can move there and start in on longer term projects.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
