incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
Date Mon, 13 Aug 2012 22:20:39 GMT
Hi Carol,

historically things change when people take the time and effort to make
things happen. If we, in this apache flex project, wants GIT, mentors and
the ASF will make it happen. Infra will get full git support before, if we
are another grain of sand wanting that support.

But again, I'm defending Git, not because "it's a cool SCM", or because "is
a techy discussion", or whatever people would like to say. I'm defending
Git because I think we need it to take flex to the next level and think SVN
will not. I'm talking (or writing) from the knowledge of both systems, and
this is something not everybody in the thread discussion could say.

So I will say that people should vote for Git, because think is needed (or
almost good) for the project not becasue it has some level of support,
because we will make Infra to support it we as a group choose that concrete
SCM because the project need it.



2012/8/13 Carol Frampton <cframpto@adobe.com>

> Dave,
>
> I'd like to vote with you but I am still pondering the situation.  In your
> scenerio where would you work on something like a rewrite or a new major
> piece of functionality that might only be half done at release time.
>
> I am totally opposed to using source control not yet totally supported by
> infra.  I'd be ok with Git once that happens.
>
> Carol
>
> Sent from my Motorola ATRIX™ 4G on AT&T
>
>
> -----Original message-----
> From: Dave Fisher <dave2wave@comcast.net>
> To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
> Sent: Mon, Aug 13, 2012 21:40:03 GMT+00:00
> Subject: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
>
>
> On Aug 13, 2012, at 1:43 PM, Omar Gonzalez wrote:
>
> > On Mon, Aug 13, 2012 at 1:39 PM, Dave Fisher <dave2wave@comcast.net>
> wrote:
> >
> >> My opinion/vote is (4) - no guts, no glory - work in trunk and learn to
> >> co-operate.
> >>
> >> The vote is more about the Classic model than it is about Git  vs. SVN.
> >>
> >> To me svn tag == git branch.
> >>
> >> Regards,
> >> Dave
> >
> >
> > People that use Git a lot would strongly disagree with "svn tag == git
> > branch". For starters, SVN tags are supposed to not ever be edited, and
> Git
> > branches are used for almost all new code addition/changes in the "nvie"
> > model, so they're from from ==.
>
> I'm more thinking this from what happens in the central repository and
> what gets marked up in the history from a few comparisons I've done.
>
> When you branch in git you are marking where you are in the main repos,
> correct? If you never push it back the central repos never really cares
> about your branch, correct? So to the repository a branch is like a tag.
>
> My opinion is that git is just putting off the work of integrating diverse
> changes into a single release. I feel the same about the 3-Tier plan. It is
> just putting ALL the work of deciding what is in a release to a Release
> Manager.
>
> Really the Apache Way is for the Committers and the PPMC to share this
> responsibility. As this podling must know, you never, ever know when
> someone will exit.
>
> But go ahead and go the way you want, it is up to you all.
>
> Really what is the worst that can happen if someone plays in trunk and
> makes a mistake?
>
> Regards,
> Dave
>
> >
> > -omar
>
>


-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

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