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: What would it take to move to Git?
Date Tue, 14 Aug 2012 13:51:46 GMT
Hi Dwayne your vote doesn't count in this thread, please do it the thread
marked with [Vote] in the subject, and you must select one of the  nine
options propose by Alex Harui in the first mail of that thread

Thanks!

Carlos

El martes, 14 de agosto de 2012, Dwayne Henderson escribió:

> +1 for Git
>
> Interesting Git thread over at the OpenBSD mailinglist as well:
>
> http://comments.gmane.org/gmane.os.openbsd.misc/198461
>
> --Dwayne
>
> On Tue, Aug 14, 2012 at 12:50 AM, Carlos Rovira <
> carlos.rovira@codeoscopic.com> wrote:
>
> > If you want to support GIt, please vote in the sbiling thread! vote is
> open
> > now! :)
> >
> > 2012/8/14 jude <flexcapacitor@gmail.com>
> >
> > > I'm comfortable with SVN too but support the move to Git / GitHub
> because
> > > it is an environment that makes work like this much more efficient.
> > People
> > > can easily fork the project, make a change and get it to a working
> state.
> > > Then the main branch can easily patch those changes back in. It is also
> > an
> > > active community. There are many people that can join in, see changes
> and
> > > discussions.
> > >
> > > However, I don't know how much of GitHub's workflow we can integrate
> into
> > > an ASF project.
> > >
> > >
> > > On Mon, Aug 13, 2012 at 12:03 PM, Carlos Rovira <
> > > carlos.rovira@codeoscopic.com> wrote:
> > >
> > > > Igor, until now (flex < 4.8) I don' t see deep changes in flex core
> > like
> > > > the ones people want to perform. Spark and other features were always
> > > > "additive".
> > > >
> > > > SVN works well with such projects. But we target now other kind of
> > > changes
> > > > in the core that never was done before in flex.
> > > >
> > > > So I would like to know how would you plan to modify a core piece
> like
> > > > UIComponent with near 15k code lines while other people make other
> > > changes
> > > > without a tool like GIT...
> > > >
> > > >
> > > >
> > > > El lunes, 13 de agosto de 2012, Igor Costa escribió:
> > > >
> > > > > Carlos
> > > > >
> > > > > "But the real problem for me is that we can't target the changes
we
> > > plan
> > > > > without a tool like Git. Maybe people that does not know Git does
> not
> > > > > understand this, but we were not able to make such deep changes if
> we
> > > are
> > > > > using SVN."
> > > > >
> > > > > Flex SDK was built over 4 versions using SVN, Since Flex 3 we
> > > > open-sourced
> > > > > SDK.
> > > > >
> > > > > The only questionable thing for this entire thread is we must focus
> > on
> > > > Flex
> > > > > project not in Infra.
> > > > >
> > > > > SVN or Git whatever, we have to keep focus on Flex evolves,
> otherwise
> > > > > community members will lose their interesting on the Apache Flex
> > > project.
> > > > >
> > > > >
> > > > > To make a final statement we have to open vote and finish up and
> move
> > > to
> > > > > the next episode. Mustella, Falcon, things that are important right
> > now
> > > > for
> > > > > SDK.
> > > > >
> > > > >
> > > > > If SVN worked so well by until know, why make changes on winning
> > team?
> > > > >
> > > > >
> > > > > Regards
> > > > > ----------------------------
> > > > > Igor Costa
> > > > > www.igorcosta.com
> > > > > www.igorcosta.org
> > > > >
> > > > >
> > > > > On Mon, Aug 13, 2012 at 1:42 PM, Carlos Rovira <
> > > > > carlos.rovira@codeoscopic.com <javascript:;>> wrote:
> > > > >
> > > > > > IMHO, and taking into account that I'm only a not-binding vote...
> > > > > >
> > > > > > I don't see real arguments against Git and maybe as Omar says
> > people
> > > > does
> > > > > > not want to figth with yet another SCM...
> > > > > >
> > > > > > But the real problem for me is that we can't target the changes
> we
> > > plan
> > > > > > without a tool like Git. Maybe people that does not know Git
does
> > not
> >



-- 
Sent from Gmail Mobile

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