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 Fri, 10 Aug 2012 08:04:45 GMT
This will be optimal, and will make possible almost whatever refactor or
modification that people would want to make in Apache Flex. As I said
taking into account that Flex is targeting version 5 and is not a new
project GIT is not an option...is a must.

Projects with long history have refactoring and change needs that are
aggresive through all its codebase. Without a system like Git, I can't see
how it could be done in SVN.



> I'm not sure how the other Apache projects are doing it, but I will take a
> look.
>
> Ideally, if we went through GitHub we would create an ApacheFlex
> organization that we can add all of the committers to. Then we would be
> able to administer Issues posted on GitHub, pull request, etc. We can all
> then just fork the main repo and do all of our own experiments there and
> Pull Request them back to the main fork. The Pull Request then serves as
> the place where the community can give feedback even on committer
> contributions that want to make their way into the main line.
>
> So I would imagine the PPMC can control who has write access if we
> establish the GitHub organization.
>
> Git also has SVN commands, so we can still push to the SVN repository, like
> when we do a release if we wanted to also make release tags available on
> SVN they can be pushed to SVN from the Git cli.
>
> -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