incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <dave2w...@comcast.net>
Subject Re: [MENTORS] Current Branching Strategy Vote Results
Date Wed, 15 Aug 2012 21:04:34 GMT

On Aug 15, 2012, at 1:25 PM, Alex Harui wrote:

> 
> 
> 
> On 8/15/12 1:13 PM, "labriola@digitalprimates.net"
> <labriola@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.

If this is how the project wishes to roll then I would suggest the following sequence assuming
that Falcon is coming in a few days.

(1) Rearrange the SVN Repository for the new structure.

(2) Import Falcon into SVN.

(3) INFRA JIRA request for Git in the current supported mode. Include the Flex Git volunteers
along with the PPMC, Committer, and/or Contributor status for each.

(4) Once the Git Mirrors are ready then let the pulls begin.

(5) The Volunteers may help drive this to the desired, fully blessed, outcome faster, or they
might not, only work and time will tell. (Contributors may very well earn enough merit for
the PPMC to vote them Committer status.)

BTW - There was an #asfinfra discussion about Apache Policy and enforcing no log history rewrites
along with requiring a rebase this morning. Didn't follow it too closely, but the result was
the closing of an INFRA JIRA.

Regards,
Dave


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


Mime
View raw message