You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2012/08/10 09:40:53 UTC
What would it take to move to Git?
Would we be working off of github.com?
Who controls who has write-access?
What else do we need to worry about?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Friday, August 10, 2012, Jeff Conrad wrote:
> I went ahead and did it.
>
> I was able to clone the Apache Flex git repo both from github and
> git.apache.org. It was a 174 MB download. I've done this multiple times
> over the last hour or so. I was able to clone it on Windows 7 using Git
> Bash, inside Eclipse using the EGit plugin, and I even cloned it also on a
> vagrant box running CentOS 5.8 since I couldn't copy and paste the output
> from Git Bash.
>
> It took about 2-5 minutes to clone from the command line and significantly
> longer--over 20 minutes--to clone from inside Eclipse using the EGit
> plugin. Below is the command line output from cloning the apache repo.
>
> [vagrant@vagrant-centos ~]$ git clone git://git.apache.org/flex.git
> Cloning into 'flex'...
> remote: Counting objects: 330636, done.
> remote: Compressing objects: 100% (87765/87765), done.
> remote: Total 330636 (delta 238772), reused 325026 (delta 233243)
> Receiving objects: 100% (330636/330636), 174.64 MiB | 989 KiB/s, done.
> Resolving deltas: 100% (238772/238772), done.
>
>
>
> The git repository on Apache, and therefore the mirror on Github as well,
> has the entire revision history. There's so much history to page through
> that Eclipse actually ran out of memory while I was trying to find the
> first revision. I found it, though, after a bit of digging on github.
> Here's the commit logs from the very first open source sdk revision on
> github:
>
> https://github.com/apache/flex/commit/68afd32e95b98dae7b3f832ecbd938fbd3a90008
>
> It was on page 867 of the commit history:
> https://github.com/apache/flex/commits/trunk?page=867
>
> tl;dr
>
> 2-5 minutes on the command line
> 174 MB download
> You get a clone of the entire Apache Flex repository, with the complete
> revision history.
>
> Jeff
>
> On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
> labriola@digitalprimates.net <javascript:;>> wrote:
>
> > >OK, but the first clone will be huge? I think our import file was in
> the
> > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > network. I am testing by cloning the flex-site which worked from github.
> >
> > That is a big concern. I don't have a sense of how big it would be if all
> > of the copies of files SVN has were made singular in the git method. We
> > don't need to use github to figure it out though, we can make a local git
> > repository and try this. I am willing to do so later next week when I
> > should have time or, if someone else has time, they can do so first.
> >
> > Mike
> >
> >
> >
>
This ^^^
Another reason. Git is way faster than SVN in many facets.
I'm not sure how someone said Git branching on your local machine is slow.
It's damn near instant for me, as is switching between branches.
As far as Git clients for Mac, the best is http://www.git-tower.com/
It's extremely well done, I don't mention it originally cuz it's commercial.
SmartGit is a good alternative for Mac and PC.
I strongly recommend Tower.
-omar
Re: What would it take to move to Git?
Posted by Gordon Smith <go...@adobe.com>.
> the very first open source sdk revision
A blast from the past... I committed that!
Sent from my iPad
On Aug 10, 2012, at 7:22 PM, "Jeff Conrad" <je...@gmail.com> wrote:
> I went ahead and did it.
>
> I was able to clone the Apache Flex git repo both from github and
> git.apache.org. It was a 174 MB download. I've done this multiple times
> over the last hour or so. I was able to clone it on Windows 7 using Git
> Bash, inside Eclipse using the EGit plugin, and I even cloned it also on a
> vagrant box running CentOS 5.8 since I couldn't copy and paste the output
> from Git Bash.
>
> It took about 2-5 minutes to clone from the command line and significantly
> longer--over 20 minutes--to clone from inside Eclipse using the EGit
> plugin. Below is the command line output from cloning the apache repo.
>
> [vagrant@vagrant-centos ~]$ git clone git://git.apache.org/flex.git
> Cloning into 'flex'...
> remote: Counting objects: 330636, done.
> remote: Compressing objects: 100% (87765/87765), done.
> remote: Total 330636 (delta 238772), reused 325026 (delta 233243)
> Receiving objects: 100% (330636/330636), 174.64 MiB | 989 KiB/s, done.
> Resolving deltas: 100% (238772/238772), done.
>
>
>
> The git repository on Apache, and therefore the mirror on Github as well,
> has the entire revision history. There's so much history to page through
> that Eclipse actually ran out of memory while I was trying to find the
> first revision. I found it, though, after a bit of digging on github.
> Here's the commit logs from the very first open source sdk revision on
> github:
> https://github.com/apache/flex/commit/68afd32e95b98dae7b3f832ecbd938fbd3a90008
>
> It was on page 867 of the commit history:
> https://github.com/apache/flex/commits/trunk?page=867
>
> tl;dr
>
> 2-5 minutes on the command line
> 174 MB download
> You get a clone of the entire Apache Flex repository, with the complete
> revision history.
>
> Jeff
>
> On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
> labriola@digitalprimates.net> wrote:
>
>>> OK, but the first clone will be huge? I think our import file was in the
>> 10's of GBs. I'm afraid to try to clone the flex project over my home
>> network. I am testing by cloning the flex-site which worked from github.
>>
>> That is a big concern. I don't have a sense of how big it would be if all
>> of the copies of files SVN has were made singular in the git method. We
>> don't need to use github to figure it out though, we can make a local git
>> repository and try this. I am willing to do so later next week when I
>> should have time or, if someone else has time, they can do so first.
>>
>> Mike
>>
>>
>>
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
On Sat, Aug 11, 2012 at 10:33 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 8/11/12 2:45 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> > Hi Alex,
> >
> > great to see you on Git now! :)
> >
> >
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the initial branch.
> Why is using a local branch important?
>
> > When you finish, merge with final. You can as well publish your feature
> > branch in remote to let others see it and help with your feature.
> >
> > You must take into account that commits should be atomic in order to be
> >
> > Another great thing of Git is that when a released is planned the rest of
> > the time can continue working and commiting work without the need to
> > "freeze" commits due to the distributed nature of the system :)
> Is this because of a branching strategy or is there something about Git
> that
> makes this easier?
> >
>
Because in Git, you "commit" locally. Only when you do a "push", the
remote repo is updated. Here is a nice article explaining the concepts [1]
[1] http://gitready.com/beginner/2009/01/21/pushing-and-pulling.html
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
What are the commands you are using?
On Sat, Aug 11, 2012 at 11:29 PM, Om <bi...@gmail.com> wrote:
> I am on it.
>
> On Sat, Aug 11, 2012 at 11:28 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Update: I am unable to commit. Can any other committer try to commit a
>> change to some test file like SVN-TEST.txt?
>>
>> I got:
>>
>> "fatal: The remote end hung up unexpectedly"
>>
>> when trying to push to git://git.apache.org/flex.git and:
>>
>> "fatal: https://git-wip-us.apache.org/repos/asf/flex.git/info/refsnot
>> found: did you run git update-server-info on the server?"
>>
>> when pointing to "https://git-wip-us.apache.org/repos/asf/flex.git" as
>> described here [1].
>>
>> Can some other committer try it out?
>>
>> [1] https://git-wip-us.apache.org/
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
I am on it.
On Sat, Aug 11, 2012 at 11:28 PM, Alex Harui <ah...@adobe.com> wrote:
> Update: I am unable to commit. Can any other committer try to commit a
> change to some test file like SVN-TEST.txt?
>
> I got:
>
> "fatal: The remote end hung up unexpectedly"
>
> when trying to push to git://git.apache.org/flex.git and:
>
> "fatal: https://git-wip-us.apache.org/repos/asf/flex.git/info/refs not
> found: did you run git update-server-info on the server?"
>
> when pointing to "https://git-wip-us.apache.org/repos/asf/flex.git" as
> described here [1].
>
> Can some other committer try it out?
>
> [1] https://git-wip-us.apache.org/
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
Update: I am unable to commit. Can any other committer try to commit a
change to some test file like SVN-TEST.txt?
I got:
"fatal: The remote end hung up unexpectedly"
when trying to push to git://git.apache.org/flex.git and:
"fatal: https://git-wip-us.apache.org/repos/asf/flex.git/info/refs not
found: did you run git update-server-info on the server?"
when pointing to "https://git-wip-us.apache.org/repos/asf/flex.git" as
described here [1].
Can some other committer try it out?
[1] https://git-wip-us.apache.org/
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Saturday, August 11, 2012, Alex Harui wro
>
>
>
>
> On 8/11/12 2:45 AM, "Carlos Rovira" <carlos.rovira@codeoscopic.com<javascript:;>>
> wrote:
>
> > Hi Alex,
> >
> > great to see you on Git now! :)
> >
> >
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the initial branch.
> Why is using a local branch important?
A combination of the branching strategy and using 'git rebase' which helps
to have a cleaner repo history by playing back updates to the branch along
with yours in the right order, to resolve conflict as if both people were
committing one after the other.
It's the common practice because branching is fast and cheap (disk size).
It lets u 'go to town' on code that could lead to big changes while
committing often and not having to worry about committing things that
aren't complete. It's then up to you if you want to keep the branch local
until you finish, or you can publish it to the remote so another dev can
help you with it. You can merge commits from your local working copy from
the remote repo.
> > When you finish, merge with final. You can as well publish your feature
> > branch in remote to let others see it and help with your feature.
> >
> > You must take into account that commits should be atomic in order to be
> >
> > Another great thing of Git is that when a released is planned the rest of
> > the time can continue working and commiting work without the need to
> > "freeze" commits due to the distributed nature of the system :)
> Is this because of a branching strategy or is there something about Git
> that
> makes this easier?
-omar
>
>
RE: What would it take to move to Git?
Posted by "Guthmann, Scott" <sg...@on3solutions.com>.
> IMHO, I do not accept for Git move right now.
> We must continue in SVN this means that projects keep going. Maybe when we have a solid proper release like 5.0 we should move to git.
I have to agree with Igor on this topic. I realize how much fun it is to debate tools and different schools of thought on technology choices. I am also willing to concede that Git is a better tool than SVN - (I have no idea, obviously. And, iIt isn't relevant to my point) But because SVN is the default for Apache projects and Infra would provide less support, this piece of evidence tells me that the project would be worse off by a great deal by moving to a tool with less support. Even though Apache Flex has really smart contributors, commenters, and committers currently that do not need support from Infra - who is to say this will always be the case? Because of reasons of sustainability & additional support available for SVN that is not available for Git - it seems like a poor idea to choose a tool that we know has less support - doesn't it?
> Right now is a waste of time trying to procrastinating things that isn't relevant to the project goals.
Again - this statement is very compelling to me. [So fun to debate about these things!] that have very little or nothing to do with moving the project forward and making the SDK less buggy, more feature rich, easier to use, less risky for firms to rely on, etc... Igor has been persuasive with me on this point!
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
IMHO, I do not accept for Git move right now.
We must continue in SVN this means that projects keep going. Maybe when we
have a solid proper release like 5.0 we should move to git.
Right now is a waste of time trying to procrastinating things that isn't
relevant to the project goals.
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Sun, Aug 12, 2012 at 11:33 AM, Omar Gonzalez
<om...@gmail.com>wrote:
> On Sunday, August 12, 2012, Greg Reddin wrote:
>
> >
> >
> > Sent from my mobile device.
> >
> > On Aug 11, 2012, at 4:45 AM, Carlos Rovira <
> carlos.rovira@codeoscopic.com<javascript:;>>
> > wrote:
> >
> > > When you want to plan a feature make a local branch to make your
> > > development, better than start to make it directly on the initial
> branch.
> > > When you finish, merge with final. You can as well publish your
> feature
> > > branch in remote to let others see it and help with your feature.
> >
> > These are the kind of statements I'm not too comfortable with right now.
> > At Apache we have to do things collaboratively. Your local branch should
> be
> > very short-lived before you share it with the rest of the dev team. We
> > don't want to see your feature when you're done with it. We want to see
> it
> > as it develops and maybe contribute to it or offer thoughts along the
> way.
> >
> > Greg
>
>
> It's really just a matter of when the developer is ready to start
> discussing the work, either way when a feature branch is published or not
> is kind of beside the point. The branching model works the same if wedo or
> do not publish feature branches immediately. A lot of times local branches
> get killed because the experiment goes haywire.
>
> -omar
>
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Sunday, August 12, 2012, Greg Reddin wrote:
>
>
> Sent from my mobile device.
>
> On Aug 11, 2012, at 4:45 AM, Carlos Rovira <carlos.rovira@codeoscopic.com<javascript:;>>
> wrote:
>
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the initial branch.
> > When you finish, merge with final. You can as well publish your feature
> > branch in remote to let others see it and help with your feature.
>
> These are the kind of statements I'm not too comfortable with right now.
> At Apache we have to do things collaboratively. Your local branch should be
> very short-lived before you share it with the rest of the dev team. We
> don't want to see your feature when you're done with it. We want to see it
> as it develops and maybe contribute to it or offer thoughts along the way.
>
> Greg
It's really just a matter of when the developer is ready to start
discussing the work, either way when a feature branch is published or not
is kind of beside the point. The branching model works the same if wedo or
do not publish feature branches immediately. A lot of times local branches
get killed because the experiment goes haywire.
-omar
Re: What would it take to move to Git?
Posted by Greg Reddin <gr...@gmail.com>.
Sent from my mobile device.
On Aug 11, 2012, at 4:45 AM, Carlos Rovira <ca...@codeoscopic.com> wrote:
> When you want to plan a feature make a local branch to make your
> development, better than start to make it directly on the initial branch.
> When you finish, merge with final. You can as well publish your feature
> branch in remote to let others see it and help with your feature.
These are the kind of statements I'm not too comfortable with right now. At Apache we have to do things collaboratively. Your local branch should be very short-lived before you share it with the rest of the dev team. We don't want to see your feature when you're done with it. We want to see it as it develops and maybe contribute to it or offer thoughts along the way.
Greg
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> Well, you wouldn't be cherry picking from develop into master.
So everything in dev must work and be in a 100% working state in order to make a release? That means we need to somehow veto changes in feature branches before merging them with dev? So if we were to do this cheery picking people changes from dev would rarely occur (if at all), you want to be merging full branches if possible.
> I get confused w/ this one, will get back to you on this one. :)
I's guess hat you would want to keep the history. I think using this option may make more sense in a more commercial/less open project in that you may not want the internal developers commit history to be part of the source code release but have a more succinct "this feature was added" style history? But I really don't know enough about it to know.
> However, before a release branch is killed off you MUST tag it.
So to apply a patch to a previous you would branch a tag, apply the needed fix, make another release and tag it. You would then merge the fix back into dev and delete the branch. What if changes in dev meant that your fix couldn't be merged I assume you would then need to keep the branch around until it was no longer used/supported?
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Sun, Aug 12, 2012 at 12:24 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> > Why is using a local branch important?
> When using git most branches are local and not shared between developers
> unless it's needed (in my experience anyway). Although it easy to share
> between people working on a large feature - have a look at the IDE dev on
> github and yuo'll see that in action.
>
> > Is this because of a branching strategy or is there something about Git
> that
> > makes this easier?
> Mostly github (easier to branch and merge) but you still need need the
> right branching stategy and as it's easier to branch in git we are likely
> to have more need to a branch structure/rule than if we used SVN.
>
Not necessarily because of the way merging is handled. The branching
strategy is more about facilitating parallel development as opposed to
trying to avoid merge conflicts, which is usually the motivator in SVN, not
Git.
>
> I've had a deeper look at the gitflow branching structure and before we
> vote on using we might want to think about:
> - What branches are local/what are in the origin repo. Only 2 long lived
> branches in the gitflow model (ie develop and master) are stored centrally.
>
That's correct, as well as tags of Release branches before they're merged
back into trunk and dev, in case we need to perform a hotfix on a released
version.
> - Are we going to have issues with cherry picking fixes from develop into
> master causing unstable releases? May want to consider what Linus has to
> say on the issue on the issue https://lkml.org/lkml/2008/5/21/351 +
> https://lkml.org/lkml/2010/11/12/291. (I do like the idea of stable and
> next branches mentioned in the second email).
>
Well, you wouldn't be cherry picking from develop into master. The only way
code gets into Master is from a Release branch. Release branches are made
directly from Dev. Dev only contains code that has been added to the source
either via a Hotfix branch or a Feature branch. When you're done with a
Feature branch and its time to merge the code into Dev usually an
'Integration' branch is made locally in order to merge the Feature branch
back into the an integration branch that is freshly made from Dev. This is
where you make sure the Feature branch code doesn't break the stability of
Dev, if it does the issues should be fixed in the temporary Integration
branch and then merged back into Dev, at which point you can kill both the
local Feature and Integration branches.
> - Think carefully about the no fast forward option and it's effects. Look
> at comments as it may be being incorrectly being used. Do we want it on by
> default as suggested?
>
I get confused w/ this one, will get back to you on this one. :)
- Do we want release branches to be short lived? Main issue this this is (I
> think) is that's hard to patch issues in previous releases and means any
> serious bug fix allways going the latest release forcing user of the SDK to
> allway be on the latest version. I'm really not sure on this one. However
> note than in Linux development has a stable branch for each release and not
> a master as such ( see development model at
> http://en.wikipedia.org/wiki/Linux_kernel).
> Thanks,
> Justin
This is incorrect. Release branches are short lived, yes. However, before a
release branch is killed off you MUST tag it. The whole purpose of the tag
is to mark the point in time at which the Release branch was done being
worked on and sent to Master. When you merge a release branch to Master its
the equivalent of producing a release, that is why you must tag it
"v.1.0.1". Then you kill the Release branch. If two weeks later a bug that
must be fixed is needed, but new features are already being developed in
Dev, then you create a Hotfix branch from the "v.1.0.1" tag and go to town
fixing the emergency bug. Once that bug is ready to be deployed you can use
it as a release branch to update version numbers, and do all the other
things required for a release, tag it "v.1.0.2", merge it to Master, merge
it to Dev, and destroy the Hotfix branch.
So in short, you can make fixes to any version at any time.
-omar
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Why is using a local branch important?
When using git most branches are local and not shared between developers unless it's needed (in my experience anyway). Although it easy to share between people working on a large feature - have a look at the IDE dev on github and yuo'll see that in action.
> Is this because of a branching strategy or is there something about Git that
> makes this easier?
Mostly github (easier to branch and merge) but you still need need the right branching stategy and as it's easier to branch in git we are likely to have more need to a branch structure/rule than if we used SVN.
I've had a deeper look at the gitflow branching structure and before we vote on using we might want to think about:
- What branches are local/what are in the origin repo. Only 2 long lived branches in the gitflow model (ie develop and master) are stored centrally.
- Are we going to have issues with cherry picking fixes from develop into master causing unstable releases? May want to consider what Linus has to say on the issue on the issue https://lkml.org/lkml/2008/5/21/351 + https://lkml.org/lkml/2010/11/12/291. (I do like the idea of stable and next branches mentioned in the second email).
- Think carefully about the no fast forward option and it's effects. Look at comments as it may be being incorrectly being used. Do we want it on by default as suggested?
- Do we want release branches to be short lived? Main issue this this is (I think) is that's hard to patch issues in previous releases and means any serious bug fix allways going the latest release forcing user of the SDK to allway be on the latest version. I'm really not sure on this one. However note than in Linux development has a stable branch for each release and not a master as such ( see development model at http://en.wikipedia.org/wiki/Linux_kernel).
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/11/12 2:45 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
> Hi Alex,
>
> great to see you on Git now! :)
>
>
> When you want to plan a feature make a local branch to make your
> development, better than start to make it directly on the initial branch.
Why is using a local branch important?
> When you finish, merge with final. You can as well publish your feature
> branch in remote to let others see it and help with your feature.
>
> You must take into account that commits should be atomic in order to be
>
> Another great thing of Git is that when a released is planned the rest of
> the time can continue working and commiting work without the need to
> "freeze" commits due to the distributed nature of the system :)
Is this because of a branching strategy or is there something about Git that
makes this easier?
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex,
great to see you on Git now! :)
First get a free Git client that will help you to get on track with this
new SCM. As we discussed before the best *free* clients are smart git on
windows and sourcetree on mac.
One thing to point now that you tried it is that philosophy behind Git is
little different from SVN.
When you want to plan a feature make a local branch to make your
development, better than start to make it directly on the initial branch.
When you finish, merge with final. You can as well publish your feature
branch in remote to let others see it and help with your feature.
You must take into account that commits should be atomic in order to be
manageable as a "cherry pick". Cherry picks let you apply a single commit
without dragging the rest of changes (merge will apply all history). Avoid
mix modifications in single commits and make groups of related files to
accomplish a single commit. When you have a group of local commits that
makes a feature make a "push" to the remote server. In git the concept of
commit has more meaning that in SVN since if you did a commit that is not
mixed with other things you can perform lot of actions, reverse the commit,
and so on...
To see remote changes perform a "fetch". To retrieve remote changes make a
"pull".
Consider to use a "stash" when you want to reset you branch without lossing
you work (it will be packed in a named patch that you can apply at a later
time).
One great thing to take into account is that you can't push to remote until
you resolve conflicts. This allow people resolve "in home" all conflicts
and not break the remote branch. But this require to fix a pass some test
before make the push.
Another great thing of Git is that when a released is planned the rest of
the time can continue working and commiting work without the need to
"freeze" commits due to the distributed nature of the system :)
Hope you like Git and will envision the possibilities in a near future when
we try to plan aggresive changes that make many people be productive as
they do many different task that will go to the main branch at different
time.
2012/8/11 Alex Harui <ah...@adobe.com>
>
>
>
> On 8/10/12 8:07 PM, "Omar Gonzalez" <om...@gmail.com> wrote:
>
> >
> > Went ahead and tried it myself also, here's my console log:
> >
> > quintessa:GitHub grimlock$ git clone git://git.apache.org/flex.git
> > Cloning into 'flex'...
> > remote: Counting objects: 330636, done.
> > remote: Compressing objects: 100% (87765/87765), done.
> > Receiving objects: 100% (330636/330636), 174.63 MiB | 364 KiB/s, done.
> > remote: Total 330636 (delta 238777), reused 325021 (delta 233243)
> > Resolving deltas: 100% (238777/238777), done.
> > quintessa:GitHub grimlock$ du -sh ./flex/
> > 799M ./flex/
> >
> Thanks Jeff and Omar. It started working for me too. It took about an
> hour
> or so on my home network which is actually way better than SVN, IIRC.
>
> Tomorrow I will try to commit something and if it works, we'll start a vote
> on Monday.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
--
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
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
I'm with Omar,
it's like to point if people has computer to develop or not. It's up to
contributors to have the skills, time and needs required . The key point
here is the real needs for apache flex next iteration(s) and if SVN can
handle it or not. In my opinion is impossible to use SVN for what people
have in mind, and for this reason we are considering GIT.
(apart from that GIT is faster than SVN, so it requieres less
bandwidth...but this again has nothing to do here)
2012/8/11 Omar Gonzalez <om...@gmail.com>
> I'm not saying everyone has DSL+.
>
> I'm just saying connection speeds should not be considered for this
> decision, sorry.
>
> -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
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
I'm not saying everyone has DSL+.
I'm just saying connection speeds should not be considered for this
decision, sorry.
-omar
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
And we can't agree that all has DSL2+
Most people on world has 1Mb link shared connection with low latency.
That's why Apache has mirrors for each one of them.
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Sat, Aug 11, 2012 at 1:57 AM, Omar Gonzalez <om...@gmail.com>wrote:
> On Friday, August 10, 2012, Igor Costa wrote:
>
> > [image: Inline image 1]
> >
> >
> > With your such internet is pretty damn fast.
> >
> > With 56Kb/s transfer rate it take centuries. Specially for cloning.
> >
> >
> > Of course will only happen first time when you clone it, than switch over
> > branches are quite fast.
> >
> >
> >
> >
> > ----------------------------
> > Igor Costa
> > www.igorcosta.com
> > www.igorcosta.org
> >
>
> Agreed its much faster on a good cable connection as opposed to 56kb/s.
>
> But we can't vote against something because some people are on dial up. It
> sucks, but that can't be a criterion for SCM choice.
>
> -omar
>
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Friday, August 10, 2012, Igor Costa wrote:
> [image: Inline image 1]
>
>
> With your such internet is pretty damn fast.
>
> With 56Kb/s transfer rate it take centuries. Specially for cloning.
>
>
> Of course will only happen first time when you clone it, than switch over
> branches are quite fast.
>
>
>
>
> ----------------------------
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
>
Agreed its much faster on a good cable connection as opposed to 56kb/s.
But we can't vote against something because some people are on dial up. It
sucks, but that can't be a criterion for SCM choice.
-omar
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
[image: Inline image 1]
With your such internet is pretty damn fast.
With 56Kb/s transfer rate it take centuries. Specially for cloning.
Of course will only happen first time when you clone it, than switch over
branches are quite fast.
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Sat, Aug 11, 2012 at 12:07 AM, Omar Gonzalez
<om...@gmail.com>wrote:
> >
> >
> > On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
> > labriola@digitalprimates.net> wrote:
> >
> > > >OK, but the first clone will be huge? I think our import file was in
> > the
> > > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > > network. I am testing by cloning the flex-site which worked from
> github.
> > >
> > > That is a big concern. I don't have a sense of how big it would be if
> all
> > > of the copies of files SVN has were made singular in the git method. We
> > > don't need to use github to figure it out though, we can make a local
> git
> > > repository and try this. I am willing to do so later next week when I
> > > should have time or, if someone else has time, they can do so first.
> > >
> > > Mike
> >
>
> Went ahead and tried it myself also, here's my console log:
>
> quintessa:GitHub grimlock$ git clone git://git.apache.org/flex.git
> Cloning into 'flex'...
> remote: Counting objects: 330636, done.
> remote: Compressing objects: 100% (87765/87765), done.
> Receiving objects: 100% (330636/330636), 174.63 MiB | 364 KiB/s, done.
> remote: Total 330636 (delta 238777), reused 325021 (delta 233243)
> Resolving deltas: 100% (238777/238777), done.
> quintessa:GitHub grimlock$ du -sh ./flex/
> 799M ./flex/
>
> The download is 174.63 MB.
> The /flex folder once checked out is 799M.
>
> I also tried making some branches, it was instant.
> Switching between branches, also instant.
> These would be local branches.
>
> Publishing branches back to the remote should also be fast, as it does not
> reupload the entire branch fileset, Git is smarter than that.
>
> -omar
>
Re: What would it take to move to Git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Aug 13, 2012 at 6:13 PM, Omar Gonzalez
<om...@gmail.com> wrote:
> ...The way Apache (doesn't) supports Git kind of sucks anyhow, as it
> essentially leaves sVN as the primary and uses Git as an interface
> basically....
No.
That's only one of the options, please read s.apache.org/flex_git_options
-Bertrand
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/13/12 12 :13PM, "Omar Gonzalez" <om...@gmail.com> wrote:
>On Monday, August 13, 2012, Carol Frampton wrote:
>
>>
>>
>> On 8/11/12 2 :30AM, "Alex Harui" <aharui@adobe.com <javascript:;>>
>>wrote:
>>
>> >
>> >Tomorrow I will try to commit something and if it works, we'll start a
>> >vote
>> >on Monday.
>>
>> I assume/hope the VOTE would be at least 48 hours since I now have to
>>drop
>> everything I was working on to go learn enough about Git to vote.
>>
>> I would also like to paste from one of Bertrand's emails last week to
>> reiterate his warning message [1]:
>>
>> Let me add one BIG WARNING as a mentor: branches might be much easier
>> to manage with Git, but if a move to Git is a way to avoid agreeing on
>> how branches are managed, that won't help IMO. I would recommend
>> sorting that problem (which is a community problem, not a technical
>> one) in svn first before considering a move.
>>
>>
>> As far as I can figure there has been no agreement on branching
>>strategy.
>>
>> Carol
>>
>> [1] http://markmail.org/message/pv6rfhec2hnefggo
>>
>>
>I wouldn't vote for Git at this point as I feels there is too much push
>back from people that don't want to learn it, because none of the
>arguments
>put against it are really that convincing, it's mostly that people just
>don't want to learn it.
>
>The way Apache (doesn't) supports Git kind of sucks anyhow, as it
>essentially leaves sVN as the primary and uses Git as an interface
>basically.
>
>I will be doing all my work in Git and usin git svn dcommit as soon as I
>can get it set up, whatever branching strategy gets agreed upon, anyhow.
>
>In regard to the branching strategy, I still believe the Git Branching
>Model is the way to go, even in SVN. Everything else that has been
>proposed
>sounds like chaos and has all been presented without a very clear
>workflow.
>The GBM is clear, thought out, and in my experience using it works
>extremely well.
I don't disagree (or agree) that the Git branching strategy might be the
best but I think whatever the branching strategy is proposed needs to be
spelled out so everyone is on the same page on what that means for each
case we've been discussing (short-term dev, longer term dev that might not
be finished for the next release, hot fixes, etc). We need to be very
clear on what we are all agreeing on so people don't have to know what the
Git branching strategy or any other strategy means from just a few
keywords.
Carol
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Monday, August 13, 2012, Carol Frampton wrote:
>
>
> On 8/11/12 2 :30AM, "Alex Harui" <aharui@adobe.com <javascript:;>> wrote:
>
> >
> >Tomorrow I will try to commit something and if it works, we'll start a
> >vote
> >on Monday.
>
> I assume/hope the VOTE would be at least 48 hours since I now have to drop
> everything I was working on to go learn enough about Git to vote.
>
> I would also like to paste from one of Bertrand's emails last week to
> reiterate his warning message [1]:
>
> Let me add one BIG WARNING as a mentor: branches might be much easier
> to manage with Git, but if a move to Git is a way to avoid agreeing on
> how branches are managed, that won't help IMO. I would recommend
> sorting that problem (which is a community problem, not a technical
> one) in svn first before considering a move.
>
>
> As far as I can figure there has been no agreement on branching strategy.
>
> Carol
>
> [1] http://markmail.org/message/pv6rfhec2hnefggo
>
>
I wouldn't vote for Git at this point as I feels there is too much push
back from people that don't want to learn it, because none of the arguments
put against it are really that convincing, it's mostly that people just
don't want to learn it.
The way Apache (doesn't) supports Git kind of sucks anyhow, as it
essentially leaves sVN as the primary and uses Git as an interface
basically.
I will be doing all my work in Git and usin git svn dcommit as soon as I
can get it set up, whatever branching strategy gets agreed upon, anyhow.
In regard to the branching strategy, I still believe the Git Branching
Model is the way to go, even in SVN. Everything else that has been proposed
sounds like chaos and has all been presented without a very clear workflow.
The GBM is clear, thought out, and in my experience using it works
extremely well.
-omar
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/11/12 2 :30AM, "Alex Harui" <ah...@adobe.com> wrote:
>
>Tomorrow I will try to commit something and if it works, we'll start a
>vote
>on Monday.
I assume/hope the VOTE would be at least 48 hours since I now have to drop
everything I was working on to go learn enough about Git to vote.
I would also like to paste from one of Bertrand's emails last week to
reiterate his warning message [1]:
Let me add one BIG WARNING as a mentor: branches might be much easier
to manage with Git, but if a move to Git is a way to avoid agreeing on
how branches are managed, that won't help IMO. I would recommend
sorting that problem (which is a community problem, not a technical
one) in svn first before considering a move.
As far as I can figure there has been no agreement on branching strategy.
Carol
[1] http://markmail.org/message/pv6rfhec2hnefggo
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/10/12 8:07 PM, "Omar Gonzalez" <om...@gmail.com> wrote:
>
> Went ahead and tried it myself also, here's my console log:
>
> quintessa:GitHub grimlock$ git clone git://git.apache.org/flex.git
> Cloning into 'flex'...
> remote: Counting objects: 330636, done.
> remote: Compressing objects: 100% (87765/87765), done.
> Receiving objects: 100% (330636/330636), 174.63 MiB | 364 KiB/s, done.
> remote: Total 330636 (delta 238777), reused 325021 (delta 233243)
> Resolving deltas: 100% (238777/238777), done.
> quintessa:GitHub grimlock$ du -sh ./flex/
> 799M ./flex/
>
Thanks Jeff and Omar. It started working for me too. It took about an hour
or so on my home network which is actually way better than SVN, IIRC.
Tomorrow I will try to commit something and if it works, we'll start a vote
on Monday.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
>
>
> On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
> labriola@digitalprimates.net> wrote:
>
> > >OK, but the first clone will be huge? I think our import file was in
> the
> > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > network. I am testing by cloning the flex-site which worked from github.
> >
> > That is a big concern. I don't have a sense of how big it would be if all
> > of the copies of files SVN has were made singular in the git method. We
> > don't need to use github to figure it out though, we can make a local git
> > repository and try this. I am willing to do so later next week when I
> > should have time or, if someone else has time, they can do so first.
> >
> > Mike
>
Went ahead and tried it myself also, here's my console log:
quintessa:GitHub grimlock$ git clone git://git.apache.org/flex.git
Cloning into 'flex'...
remote: Counting objects: 330636, done.
remote: Compressing objects: 100% (87765/87765), done.
Receiving objects: 100% (330636/330636), 174.63 MiB | 364 KiB/s, done.
remote: Total 330636 (delta 238777), reused 325021 (delta 233243)
Resolving deltas: 100% (238777/238777), done.
quintessa:GitHub grimlock$ du -sh ./flex/
799M ./flex/
The download is 174.63 MB.
The /flex folder once checked out is 799M.
I also tried making some branches, it was instant.
Switching between branches, also instant.
These would be local branches.
Publishing branches back to the remote should also be fast, as it does not
reupload the entire branch fileset, Git is smarter than that.
-omar
Re: What would it take to move to Git?
Posted by Jeff Conrad <je...@gmail.com>.
I went ahead and did it.
I was able to clone the Apache Flex git repo both from github and
git.apache.org. It was a 174 MB download. I've done this multiple times
over the last hour or so. I was able to clone it on Windows 7 using Git
Bash, inside Eclipse using the EGit plugin, and I even cloned it also on a
vagrant box running CentOS 5.8 since I couldn't copy and paste the output
from Git Bash.
It took about 2-5 minutes to clone from the command line and significantly
longer--over 20 minutes--to clone from inside Eclipse using the EGit
plugin. Below is the command line output from cloning the apache repo.
[vagrant@vagrant-centos ~]$ git clone git://git.apache.org/flex.git
Cloning into 'flex'...
remote: Counting objects: 330636, done.
remote: Compressing objects: 100% (87765/87765), done.
remote: Total 330636 (delta 238772), reused 325026 (delta 233243)
Receiving objects: 100% (330636/330636), 174.64 MiB | 989 KiB/s, done.
Resolving deltas: 100% (238772/238772), done.
The git repository on Apache, and therefore the mirror on Github as well,
has the entire revision history. There's so much history to page through
that Eclipse actually ran out of memory while I was trying to find the
first revision. I found it, though, after a bit of digging on github.
Here's the commit logs from the very first open source sdk revision on
github:
https://github.com/apache/flex/commit/68afd32e95b98dae7b3f832ecbd938fbd3a90008
It was on page 867 of the commit history:
https://github.com/apache/flex/commits/trunk?page=867
tl;dr
2-5 minutes on the command line
174 MB download
You get a clone of the entire Apache Flex repository, with the complete
revision history.
Jeff
On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
labriola@digitalprimates.net> wrote:
> >OK, but the first clone will be huge? I think our import file was in the
> 10's of GBs. I'm afraid to try to clone the flex project over my home
> network. I am testing by cloning the flex-site which worked from github.
>
> That is a big concern. I don't have a sense of how big it would be if all
> of the copies of files SVN has were made singular in the git method. We
> don't need to use github to figure it out though, we can make a local git
> repository and try this. I am willing to do so later next week when I
> should have time or, if someone else has time, they can do so first.
>
> Mike
>
>
>
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
Om,
Forking on github is fast, try to fork on your machine.
99% knows SVN based on answers gave in the thread.
Regards
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Fri, Aug 10, 2012 at 7:53 PM, Om <bi...@gmail.com> wrote:
> On Fri, Aug 10, 2012 at 3:37 PM, Igor Costa <ig...@gmail.com> wrote:
>
> > As Carol, Gordon said, We must keep using SVN aside fact that is
> supported
> > by Apache Foundation.
> >
> > Git is cool and is on stage now, but Flex has a HUGE source code base
> and
> > isn't easy to fork on github specially if you willing to download to your
> > machine.
> >
>
> > Likely getting truck carried by volks.
> >
> >
> I am not sure what you mean, but it took less than 10 seconds for me to
> fork Apache Flex into my github account:
> https://github.com/bigosmallm/flex.
>
>
>
> > We could use git only for mirroring the code or even for docs. SVN 99% of
> > people at list knows it. Git too few.
> >
> >
> Not sure where you are getting this statistic from... Also remember that
> you did not know SVN before you knew it ;-)
>
>
> >
> > IMHO!
> >
> >
> > ----------------------------
> > Igor Costa
> > www.igorcosta.com
> > www.igorcosta.org
> >
> >
> > On Fri, Aug 10, 2012 at 7:01 PM, Carlos Rovira <
> > carlos.rovira@codeoscopic.com> wrote:
> >
> > > If you are on a Mac I strongly recommend source tree from attlasian. I
> > > think is the better tool for git ever created. In windows I think smart
> > git
> > > is the option. My experience with egit was no so good.
> > >
> > > El viernes, 10 de agosto de 2012, Michael A. Labriola escribió:
> > >
> > > > >OK, but the first clone will be huge? I think our import file was
> in
> > > the
> > > > 10's of GBs. I'm afraid to try to clone the flex project over my
> home
> > > > network. I am testing by cloning the flex-site which worked from
> > github.
> > > >
> > > > That is a big concern. I don't have a sense of how big it would be if
> > all
> > > > of the copies of files SVN has were made singular in the git method.
> We
> > > > don't need to use github to figure it out though, we can make a local
> > git
> > > > repository and try this. I am willing to do so later next week when I
> > > > should have time or, if someone else has time, they can do so first.
> > > >
> > > > Mike
> > > >
> > > >
> > > >
> > >
> > > --
> > > Sent from Gmail Mobile
> > >
> >
>
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
On Fri, Aug 10, 2012 at 3:37 PM, Igor Costa <ig...@gmail.com> wrote:
> As Carol, Gordon said, We must keep using SVN aside fact that is supported
> by Apache Foundation.
>
> Git is cool and is on stage now, but Flex has a HUGE source code base and
> isn't easy to fork on github specially if you willing to download to your
> machine.
>
> Likely getting truck carried by volks.
>
>
I am not sure what you mean, but it took less than 10 seconds for me to
fork Apache Flex into my github account: https://github.com/bigosmallm/flex.
> We could use git only for mirroring the code or even for docs. SVN 99% of
> people at list knows it. Git too few.
>
>
Not sure where you are getting this statistic from... Also remember that
you did not know SVN before you knew it ;-)
>
> IMHO!
>
>
> ----------------------------
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
>
>
> On Fri, Aug 10, 2012 at 7:01 PM, Carlos Rovira <
> carlos.rovira@codeoscopic.com> wrote:
>
> > If you are on a Mac I strongly recommend source tree from attlasian. I
> > think is the better tool for git ever created. In windows I think smart
> git
> > is the option. My experience with egit was no so good.
> >
> > El viernes, 10 de agosto de 2012, Michael A. Labriola escribió:
> >
> > > >OK, but the first clone will be huge? I think our import file was in
> > the
> > > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > > network. I am testing by cloning the flex-site which worked from
> github.
> > >
> > > That is a big concern. I don't have a sense of how big it would be if
> all
> > > of the copies of files SVN has were made singular in the git method. We
> > > don't need to use github to figure it out though, we can make a local
> git
> > > repository and try this. I am willing to do so later next week when I
> > > should have time or, if someone else has time, they can do so first.
> > >
> > > Mike
> > >
> > >
> > >
> >
> > --
> > Sent from Gmail Mobile
> >
>
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Mon, Aug 13, 2012 at 9:53 AM, Igor Costa <ig...@gmail.com> wrote:
> 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.
>
That doesn't mean we shouldn't question moving to a better system. Git is a
better SCM system than SVN in many aspects. Flex was built on SVN, sure,
but under the control of a corporate entity. It is now completely open
source, its quite different having many developers whose activity is coming
in and out of the project.
>
> The only questionable thing for this entire thread is we must focus on Flex
> project not in Infra.
>
The SCM infrastructure is important. If you don't view it as such then I
believe that you should reconsider, it is extremely important.
>
> SVN or Git whatever, we have to keep focus on Flex evolves, otherwise
> community members will lose their interesting on the Apache Flex project.
>
Again, this is about Flex, and moving it forward, in the best direction. My
argument is that Git is the best direction for it, and I've stated reasons
for that throughout the thread. Everyone's argument against it has just
been "i dont want to learn X", but in my opinion, nothing of substance.
>
>
> 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.
>
>
Make other email threads about this and start the conversation. This thread
is about moving to Git.
>
> If SVN worked so well by until know, why make changes on winning team?
>
SVN worked so well under a corporate entity with EMPLOYEES that had to
follow a _lead_. We are not employees, we do not have a lead and we have
lots of devs that will be in and out of the code. Git will support this
much better than SVN.
>
>
> Regards
> ----------------------------
> Igor Costa
> www.igorcosta.com
> www.igorcosta.org
>
The SCM of the project is just as important as any issue.
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
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 <fl...@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
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/14/12 6:47 AM, "João Fernandes" <jo...@gmail.com>
wrote:
>
> Is there any pitfall for using GIT mirroring the SVN repository and having
> people commiting in both SVN/GIT?
>
The information I read is that you have to be very careful about how you use
Git if you plan to commit back via Git-SVN because it is still SVN merging
under the covers.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by jude <fl...@gmail.com>.
A little late to the discussion but a great article on why you should
switch to git (from subversion) with a brief overview of Git,
http://teamtreehouse.com/blog/why-you-should-switch-from-subversion-to-git
On Tue, Aug 14, 2012 at 1:02 PM, Carol Frampton <cf...@adobe.com> wrote:
>
>
> On 8/14/12 11 :58AM, "Carlos Rovira" <ca...@codeoscopic.com>
> wrote:
>
> >>
> >> I think the conversation and relative merits is exactly what we should
> >>be
> >> doing. The only thing I wish is that, like other areas of the project,
> >>we
> >> didn't have to wait on someone else. If we could just demonstrate the
> >> advantages of Git instead of talking about them in the abstract, I
> >>think we
> >> would have less issue. The problem here with Git is its different. And,
> >> unfortunately, without an understanding of those advantages and how they
> >> might help us longer term it is very difficult for anyone to agree that
> >>we
> >> should make that change now.
> >>
> >> The discussion is golden. I think the real question is, once we make a
> >> decision can everyone support it and move forward or does anyone take
> >>their
> >> toys and go home.
> >>
> >> Mike
> >>
> >>
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
But...if Git wasn't an option now Alex would not be listing it, isn't
it?...so If you think Git is the solution, IMHO is you should vote what you
think, because, as I said, is a valid option. If GIT ends as the preferred
solution (and there's many votes to option 9), we should go with GIT as
many other apache projects. Infra *should not* be a problem if we are
decided to make it real.
2012/8/14 Michael A. Labriola <la...@digitalprimates.net>
>
> >Then if even people like you that would vote for GIT in first instance,
> ends voting for the opposite...I think we are not doing us a favor.
>
> Carlos,
>
> Just to be clear. I didn't vote for Git in the first place. I said we
> should consider it and I still think we should. I voted the way I did as I
> also believe that moving forward now and not spending many cycles if Apache
> infra is not ready for us is important too.
>
> I would prefer we use Git. I voted based on the practicality of using it
> now.
>
> Mike
>
--
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
RE: What would it take to move to Git?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>Then if even people like you that would vote for GIT in first instance, ends voting for the opposite...I think we are not doing us a favor.
Carlos,
Just to be clear. I didn't vote for Git in the first place. I said we should consider it and I still think we should. I voted the way I did as I also believe that moving forward now and not spending many cycles if Apache infra is not ready for us is important too.
I would prefer we use Git. I voted based on the practicality of using it now.
Mike
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/14/12 11 :58AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>>
>> I think the conversation and relative merits is exactly what we should
>>be
>> doing. The only thing I wish is that, like other areas of the project,
>>we
>> didn't have to wait on someone else. If we could just demonstrate the
>> advantages of Git instead of talking about them in the abstract, I
>>think we
>> would have less issue. The problem here with Git is its different. And,
>> unfortunately, without an understanding of those advantages and how they
>> might help us longer term it is very difficult for anyone to agree that
>>we
>> should make that change now.
>>
>> The discussion is golden. I think the real question is, once we make a
>> decision can everyone support it and move forward or does anyone take
>>their
>> toys and go home.
>>
>> Mike
>>
>>
>Mike, I think we are debated long enough about GIT with lots of arguments.
>Those arguments still are not valid if people does not want to take a
>little effort: learn a new tool that only extends SVN to the better. The
>only arguments are that Apache official SCM is SVN, that there is no full
>support and that "I only want to talk about new code, but don't want to
>take the effort of know why GIT is better for the project".
>
>Then if even people like you that would vote for GIT in first instance,
>ends voting for the opposite...I think we are not doing us a favor.
>
>If we are investing lots of mails here is because many of think this is
>really important. And this should be what mentors should valorate.
>
>This decision would change the future of Flex, since people would
>colaborate or not in determinated areas of development if they feels
>comfortable with the model of development.
>
>If instead of having branch to test stuff, we must to go over dispare
>whiteboards that are isolated. That will be a total nightmare and this
>project could end without very few people investing time.
>
Carlos.
I've spent the day reading about Git. I'd have no problem switching to
Git when it becomes a supported tool so don't go saying people don't want
to spend the time learning a new tool.
If you'd rather create a branch in branches rather than in whiteboards so
you can share your work go ahead. No one is stopping you.
Carol
>
>
>
>
>--
>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
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
Guys concentrate on that matters, voting!
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Tue, Aug 14, 2012 at 12:58 PM, Carlos Rovira <
carlos.rovira@codeoscopic.com> wrote:
> >
> > I think the conversation and relative merits is exactly what we should be
> > doing. The only thing I wish is that, like other areas of the project, we
> > didn't have to wait on someone else. If we could just demonstrate the
> > advantages of Git instead of talking about them in the abstract, I think
> we
> > would have less issue. The problem here with Git is its different. And,
> > unfortunately, without an understanding of those advantages and how they
> > might help us longer term it is very difficult for anyone to agree that
> we
> > should make that change now.
> >
> > The discussion is golden. I think the real question is, once we make a
> > decision can everyone support it and move forward or does anyone take
> their
> > toys and go home.
> >
> > Mike
> >
> >
> Mike, I think we are debated long enough about GIT with lots of arguments.
> Those arguments still are not valid if people does not want to take a
> little effort: learn a new tool that only extends SVN to the better. The
> only arguments are that Apache official SCM is SVN, that there is no full
> support and that "I only want to talk about new code, but don't want to
> take the effort of know why GIT is better for the project".
>
> Then if even people like you that would vote for GIT in first instance,
> ends voting for the opposite...I think we are not doing us a favor.
>
> If we are investing lots of mails here is because many of think this is
> really important. And this should be what mentors should valorate.
>
> This decision would change the future of Flex, since people would
> colaborate or not in determinated areas of development if they feels
> comfortable with the model of development.
>
> If instead of having branch to test stuff, we must to go over dispare
> whiteboards that are isolated. That will be a total nightmare and this
> project could end without very few people investing time.
>
>
>
>
>
> --
> 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
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
>
> I think the conversation and relative merits is exactly what we should be
> doing. The only thing I wish is that, like other areas of the project, we
> didn't have to wait on someone else. If we could just demonstrate the
> advantages of Git instead of talking about them in the abstract, I think we
> would have less issue. The problem here with Git is its different. And,
> unfortunately, without an understanding of those advantages and how they
> might help us longer term it is very difficult for anyone to agree that we
> should make that change now.
>
> The discussion is golden. I think the real question is, once we make a
> decision can everyone support it and move forward or does anyone take their
> toys and go home.
>
> Mike
>
>
Mike, I think we are debated long enough about GIT with lots of arguments.
Those arguments still are not valid if people does not want to take a
little effort: learn a new tool that only extends SVN to the better. The
only arguments are that Apache official SCM is SVN, that there is no full
support and that "I only want to talk about new code, but don't want to
take the effort of know why GIT is better for the project".
Then if even people like you that would vote for GIT in first instance,
ends voting for the opposite...I think we are not doing us a favor.
If we are investing lots of mails here is because many of think this is
really important. And this should be what mentors should valorate.
This decision would change the future of Flex, since people would
colaborate or not in determinated areas of development if they feels
comfortable with the model of development.
If instead of having branch to test stuff, we must to go over dispare
whiteboards that are isolated. That will be a total nightmare and this
project could end without very few people investing time.
--
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
RE: What would it take to move to Git?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>> In my view, we still seem like a disparate group of individuals who
>> are most comfortable working alone or on small groups with great
>> amounts of autonomy. We are not a team yet & our Flex project isn't self-sustaining.
>> My evidence is this conversation debating the relative merits of our
>> options and the reasoning each commenter has given.
>I think the fact that 95 msgs have been posted to this thread shows commitment and an effort to become a team. How else do you propose we come to decisions? Mentors won't be here forever...
I think the conversation and relative merits is exactly what we should be doing. The only thing I wish is that, like other areas of the project, we didn't have to wait on someone else. If we could just demonstrate the advantages of Git instead of talking about them in the abstract, I think we would have less issue. The problem here with Git is its different. And, unfortunately, without an understanding of those advantages and how they might help us longer term it is very difficult for anyone to agree that we should make that change now.
The discussion is golden. I think the real question is, once we make a decision can everyone support it and move forward or does anyone take their toys and go home.
Mike
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Tuesday, August 14, 2012, Guthmann, Scott wrote:
> > I'm not assuming we'll moving to GIT right away but as Bertrand
> mentioned, we need to work as a team and if PPMC members aren't able to
> find a strategy for Apache Flex when it comes to source control, how is it
> going to work for code additions/changes?
>
> I think João is pointing out something important that I think we must
> understand as a group. It is a judgment call when / if the Mentors decide
> the project is ready to graduate from Podling to Project or not. I do not
> know what our Mentors are thinking - but my guess is that these are some of
> the things they are probably looking for from our project.
>
> 1) Are we able to make strategic decisions as a group correctly that give
> the Flex project the best chance for success over the long term?
> 2) When good advice (help) is given, are we willing to take it?
> 3) Do we act like a team and make decisions for the good of the team even
> when our own preferences are not being used?
> 4) Do we have a group of active & participating PPMC members who are
> actually committed to the project?
> 5) Today, we still require corporate support and mentoring to sustain the
> project. If the support and mentoring were removed, what would happen?
>
> In my view, we still seem like a disparate group of individuals who are
> most comfortable working alone or on small groups with great amounts of
> autonomy. We are not a team yet & our Flex project isn't self-sustaining.
> My evidence is this conversation debating the relative merits of our
> options and the reasoning each commenter has given.
>
So you're saying we should just all shut up and do as the mentors say for
the sake of graduating?
I think the fact that 95 msgs have been posted to this thread shows
commitment and an effort to become a team. How else do you propose we come
to decisions? Mentors won't be here forever...
-omar
RE: What would it take to move to Git?
Posted by "Guthmann, Scott" <sg...@on3solutions.com>.
> I'm not assuming we'll moving to GIT right away but as Bertrand mentioned, we need to work as a team and if PPMC members aren't able to find a strategy for Apache Flex when it comes to source control, how is it going to work for code additions/changes?
I think João is pointing out something important that I think we must understand as a group. It is a judgment call when / if the Mentors decide the project is ready to graduate from Podling to Project or not. I do not know what our Mentors are thinking - but my guess is that these are some of the things they are probably looking for from our project.
1) Are we able to make strategic decisions as a group correctly that give the Flex project the best chance for success over the long term?
2) When good advice (help) is given, are we willing to take it?
3) Do we act like a team and make decisions for the good of the team even when our own preferences are not being used?
4) Do we have a group of active & participating PPMC members who are actually committed to the project?
5) Today, we still require corporate support and mentoring to sustain the project. If the support and mentoring were removed, what would happen?
In my view, we still seem like a disparate group of individuals who are most comfortable working alone or on small groups with great amounts of autonomy. We are not a team yet & our Flex project isn't self-sustaining. My evidence is this conversation debating the relative merits of our options and the reasoning each commenter has given.
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Personaly I think the Git stuff is more easy than it seems by the amount of
mails we are sharing. But hope all this mails will serve for people to
learn more about a better SCM system.
My vote counts like yours, but if there's many non-binding votes point to
GIT and PPMCs vote for SVN but there's significante less votes, I think
PPMC should considere to take into account the community option.
If you have a project in SVN, migrate to GIT is easy. Even you can have a
project be synced with both GIT and SVN at the same time. You can ignore
files in SCMs to avoid commit files from svn to git and vicevecersa.
2012/8/14 João Fernandes <jo...@gmail.com>
> Carlos, I just can speak for myself and my vote counts nothing
> (non-binding) but I'm willing to learn anything that is required but my
> question is, besides the branching model to adopt, how much work is
> required to have everything working under GIT?
> Can it be a working process while code can keep being improved and fixed?
> Can we use both side by side till everything is ready for GIT only?
>
> I'm not assuming we'll moving to GIT right away but as Bertrand mentioned,
> we need to work as a team and if PPMC members aren't able to find a
> strategy for Apache Flex when it comes to source control, how is it going
> to work for code additions/changes?
>
> João Fernandes
>
--
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
Re: What would it take to move to Git?
Posted by João Fernandes <jo...@gmail.com>.
Carlos, I just can speak for myself and my vote counts nothing
(non-binding) but I'm willing to learn anything that is required but my
question is, besides the branching model to adopt, how much work is
required to have everything working under GIT?
Can it be a working process while code can keep being improved and fixed?
Can we use both side by side till everything is ready for GIT only?
I'm not assuming we'll moving to GIT right away but as Bertrand mentioned,
we need to work as a team and if PPMC members aren't able to find a
strategy for Apache Flex when it comes to source control, how is it going
to work for code additions/changes?
João Fernandes
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Joao,
The problem is not if flex is bigger than other projects. Or if other
bigger projects were successful using SVN.
The problem is tha flex is mature and need some changes in the deep core
classes and we will need a robust and consistent way to branch, share, test
and merge, all without break repository.
For this kind of project scenarios Git is better.
As other said before. Right now people defending was giving lots of
arguments based on articles and experiences using both SCMs, while people
against GIT only can say that apache has limit support for GIT and that
they don't want to learn a new tool and methodology.
El martes, 14 de agosto de 2012, João Fernandes escribió:
> As I said in another thread, I never used GIT but I'm willing to try it but
> I think first of all we need to pick which branching model we're going to
> follow.
>
> Is there any pitfall for using GIT mirroring the SVN repository and having
> people commiting in both SVN/GIT?
>
> While I've learned a bit about GIT in another thread and see the potential
> of GIT over SVN, I don't think SVN is unusable for a project of this size.
> There are bigger projects at Apache and they are doing just fine.
> Could they work even better under GIT? Most probably.
>
> I just hope we'll have a very detailed how-to whenever it's GIT or SVN and
> with the specific branching model detailed.
>
> João Fernandes
>
--
Sent from Gmail Mobile
Re: What would it take to move to Git?
Posted by João Fernandes <jo...@gmail.com>.
As I said in another thread, I never used GIT but I'm willing to try it but
I think first of all we need to pick which branching model we're going to
follow.
Is there any pitfall for using GIT mirroring the SVN repository and having
people commiting in both SVN/GIT?
While I've learned a bit about GIT in another thread and see the potential
of GIT over SVN, I don't think SVN is unusable for a project of this size.
There are bigger projects at Apache and they are doing just fine.
Could they work even better under GIT? Most probably.
I just hope we'll have a very detailed how-to whenever it's GIT or SVN and
with the specific branching model detailed.
João Fernandes
Re: What would it take to move to Git?
Posted by Dwayne Henderson <it...@gmail.com>.
+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 <fl...@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
> > > > > understand this, but we were not able to make such deep changes if
> we
> > > are
> > > > > using SVN.
> > > > >
> > > > > That's the real problem, and that's what we end planing the use of
> > > > > Git...this is not a techy discussion. We at work had to change two
> > > months
> > > > > ago due to hard refactors in our main product, and we changed
> because
> > > SVN
> > > > > was not letting us do such deep changes.
> > > > >
> > > > > So my vote will go for Git without doubt...if we don't use it, we
> > > should
> > > > > not be able to change things like UIComponent...hope people that
> does
> > > not
> > > > > want Git understand this.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 2012/8/13 Omar Gonzalez <omarg.developer@gmail.com <javascript:;>>
> > > > >
> > > > > > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <
> > cframpto@adobe.com
> > > <javascript:;>
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > A clarification question about Git:
> > > > > > >
> > > > > > > Would I lose the ability to look at the repro thru the web. I
> > make
> > > > use
> > > > > of
> > > > > > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc
> more
> > > > often
> > > > > > then
> > > > > > > I expected.
> > > > > > >
> > > > > > > Carol
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > You can browse it through Git HTTP:
> > > > http://git.apache.org/flex-site.git/
> > > > > >
> > > > > > Or you can view it through GitHub:
> https://github.com/apache/flex
> > > > > >
> > > > > > -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
> > > > >
> > > >
> > >
> > >
> > > --
> > > Sent from Gmail Mobile
> > >
> >
>
>
>
> --
> 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
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
If you want to support GIt, please vote in the sbiling thread! vote is open
now! :)
2012/8/14 jude <fl...@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
> > > > understand this, but we were not able to make such deep changes if we
> > are
> > > > using SVN.
> > > >
> > > > That's the real problem, and that's what we end planing the use of
> > > > Git...this is not a techy discussion. We at work had to change two
> > months
> > > > ago due to hard refactors in our main product, and we changed because
> > SVN
> > > > was not letting us do such deep changes.
> > > >
> > > > So my vote will go for Git without doubt...if we don't use it, we
> > should
> > > > not be able to change things like UIComponent...hope people that does
> > not
> > > > want Git understand this.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 2012/8/13 Omar Gonzalez <omarg.developer@gmail.com <javascript:;>>
> > > >
> > > > > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <
> cframpto@adobe.com
> > <javascript:;>
> > > >
> > > > > wrote:
> > > > >
> > > > > > A clarification question about Git:
> > > > > >
> > > > > > Would I lose the ability to look at the repro thru the web. I
> make
> > > use
> > > > of
> > > > > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more
> > > often
> > > > > then
> > > > > > I expected.
> > > > > >
> > > > > > Carol
> > > > > > >
> > > > > >
> > > > > >
> > > > > You can browse it through Git HTTP:
> > > http://git.apache.org/flex-site.git/
> > > > >
> > > > > Or you can view it through GitHub: https://github.com/apache/flex
> > > > >
> > > > > -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
> > > >
> > >
> >
> >
> > --
> > Sent from Gmail Mobile
> >
>
--
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
Re: What would it take to move to Git?
Posted by jude <fl...@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
> > > understand this, but we were not able to make such deep changes if we
> are
> > > using SVN.
> > >
> > > That's the real problem, and that's what we end planing the use of
> > > Git...this is not a techy discussion. We at work had to change two
> months
> > > ago due to hard refactors in our main product, and we changed because
> SVN
> > > was not letting us do such deep changes.
> > >
> > > So my vote will go for Git without doubt...if we don't use it, we
> should
> > > not be able to change things like UIComponent...hope people that does
> not
> > > want Git understand this.
> > >
> > >
> > >
> > >
> > >
> > > 2012/8/13 Omar Gonzalez <omarg.developer@gmail.com <javascript:;>>
> > >
> > > > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cframpto@adobe.com
> <javascript:;>
> > >
> > > > wrote:
> > > >
> > > > > A clarification question about Git:
> > > > >
> > > > > Would I lose the ability to look at the repro thru the web. I make
> > use
> > > of
> > > > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more
> > often
> > > > then
> > > > > I expected.
> > > > >
> > > > > Carol
> > > > > >
> > > > >
> > > > >
> > > > You can browse it through Git HTTP:
> > http://git.apache.org/flex-site.git/
> > > >
> > > > Or you can view it through GitHub: https://github.com/apache/flex
> > > >
> > > > -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
> > >
> >
>
>
> --
> Sent from Gmail Mobile
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
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
> > understand this, but we were not able to make such deep changes if we are
> > using SVN.
> >
> > That's the real problem, and that's what we end planing the use of
> > Git...this is not a techy discussion. We at work had to change two months
> > ago due to hard refactors in our main product, and we changed because SVN
> > was not letting us do such deep changes.
> >
> > So my vote will go for Git without doubt...if we don't use it, we should
> > not be able to change things like UIComponent...hope people that does not
> > want Git understand this.
> >
> >
> >
> >
> >
> > 2012/8/13 Omar Gonzalez <omarg.developer@gmail.com <javascript:;>>
> >
> > > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cframpto@adobe.com<javascript:;>
> >
> > > wrote:
> > >
> > > > A clarification question about Git:
> > > >
> > > > Would I lose the ability to look at the repro thru the web. I make
> use
> > of
> > > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more
> often
> > > then
> > > > I expected.
> > > >
> > > > Carol
> > > > >
> > > >
> > > >
> > > You can browse it through Git HTTP:
> http://git.apache.org/flex-site.git/
> > >
> > > Or you can view it through GitHub: https://github.com/apache/flex
> > >
> > > -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
> >
>
--
Sent from Gmail Mobile
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
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> 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
> understand this, but we were not able to make such deep changes if we are
> using SVN.
>
> That's the real problem, and that's what we end planing the use of
> Git...this is not a techy discussion. We at work had to change two months
> ago due to hard refactors in our main product, and we changed because SVN
> was not letting us do such deep changes.
>
> So my vote will go for Git without doubt...if we don't use it, we should
> not be able to change things like UIComponent...hope people that does not
> want Git understand this.
>
>
>
>
>
> 2012/8/13 Omar Gonzalez <om...@gmail.com>
>
> > On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cf...@adobe.com>
> > wrote:
> >
> > > A clarification question about Git:
> > >
> > > Would I lose the ability to look at the repro thru the web. I make use
> of
> > > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often
> > then
> > > I expected.
> > >
> > > Carol
> > > >
> > >
> > >
> > You can browse it through Git HTTP: http://git.apache.org/flex-site.git/
> >
> > Or you can view it through GitHub: https://github.com/apache/flex
> >
> > -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
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
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
understand this, but we were not able to make such deep changes if we are
using SVN.
That's the real problem, and that's what we end planing the use of
Git...this is not a techy discussion. We at work had to change two months
ago due to hard refactors in our main product, and we changed because SVN
was not letting us do such deep changes.
So my vote will go for Git without doubt...if we don't use it, we should
not be able to change things like UIComponent...hope people that does not
want Git understand this.
2012/8/13 Omar Gonzalez <om...@gmail.com>
> On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cf...@adobe.com>
> wrote:
>
> > A clarification question about Git:
> >
> > Would I lose the ability to look at the repro thru the web. I make use of
> > https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often
> then
> > I expected.
> >
> > Carol
> > >
> >
> >
> You can browse it through Git HTTP: http://git.apache.org/flex-site.git/
>
> Or you can view it through GitHub: https://github.com/apache/flex
>
> -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
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton <cf...@adobe.com> wrote:
> A clarification question about Git:
>
> Would I lose the ability to look at the repro thru the web. I make use of
> https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often then
> I expected.
>
> Carol
> >
>
>
You can browse it through Git HTTP: http://git.apache.org/flex-site.git/
Or you can view it through GitHub: https://github.com/apache/flex
-omar
Re: What would it take to move to Git?
Posted by Shannon Hicks <sh...@iotashan.com>.
To answer your questions:
1. Correct. Git is the technology, GitHub is a value-added service provider.
2. It's far easier than using SVN, but like most technologies, without a proper plan in place, merging could get tricky.
Shan
On Aug 10, 2012, at 7:50 PM, Jeffry Houser <je...@dot-com-it.com> wrote:
> On 8/10/2012 6:37 PM, Igor Costa wrote:
>> As Carol, Gordon said, We must keep using SVN aside fact that is supported
>> by Apache Foundation.
>>
>> Git is cool and is on stage now, but Flex has a HUGE source code base and
>> isn't easy to fork on github specially if you willing to download to your
>> machine.
> It is clear to me, everyone has a better understanding of such choices than me, but if you can indulge me as I ask a few clarification questions:
>
> 1) I thought Git was the version control repo; and GitHub was [in essence] a site for Git hosting; with some "social networking" stuff thrown in. Is it true that You don't have to use GitHub to use Git?
> 2) I thought the whole appeal of Git was it was very easy to fork projects (and later merge that fork back in). Is that not the case?
>
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> 203-379-0773
> --
> http://www.flextras.com?c=104
> UI Flex Components: Tested! Supported! Ready!
> --
> http://www.theflexshow.com
> http://www.jeffryhouser.com
> http://www.asktheflexpert.com
> --
> Part of the DotComIt Brain Trust
>
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
A clarification question about Git:
Would I lose the ability to look at the repro thru the web. I make use of
https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often then
I expected.
Carol
>
Re: What would it take to move to Git?
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 8/10/2012 6:37 PM, Igor Costa wrote:
> As Carol, Gordon said, We must keep using SVN aside fact that is supported
> by Apache Foundation.
>
> Git is cool and is on stage now, but Flex has a HUGE source code base and
> isn't easy to fork on github specially if you willing to download to your
> machine.
It is clear to me, everyone has a better understanding of such choices
than me, but if you can indulge me as I ask a few clarification questions:
1) I thought Git was the version control repo; and GitHub was [in
essence] a site for Git hosting; with some "social networking" stuff
thrown in. Is it true that You don't have to use GitHub to use Git?
2) I thought the whole appeal of Git was it was very easy to fork
projects (and later merge that fork back in). Is that not the case?
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: What would it take to move to Git?
Posted by Igor Costa <ig...@gmail.com>.
As Carol, Gordon said, We must keep using SVN aside fact that is supported
by Apache Foundation.
Git is cool and is on stage now, but Flex has a HUGE source code base and
isn't easy to fork on github specially if you willing to download to your
machine.
Likely getting truck carried by volks.
We could use git only for mirroring the code or even for docs. SVN 99% of
people at list knows it. Git too few.
IMHO!
----------------------------
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Fri, Aug 10, 2012 at 7:01 PM, Carlos Rovira <
carlos.rovira@codeoscopic.com> wrote:
> If you are on a Mac I strongly recommend source tree from attlasian. I
> think is the better tool for git ever created. In windows I think smart git
> is the option. My experience with egit was no so good.
>
> El viernes, 10 de agosto de 2012, Michael A. Labriola escribió:
>
> > >OK, but the first clone will be huge? I think our import file was in
> the
> > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > network. I am testing by cloning the flex-site which worked from github.
> >
> > That is a big concern. I don't have a sense of how big it would be if all
> > of the copies of files SVN has were made singular in the git method. We
> > don't need to use github to figure it out though, we can make a local git
> > repository and try this. I am willing to do so later next week when I
> > should have time or, if someone else has time, they can do so first.
> >
> > Mike
> >
> >
> >
>
> --
> Sent from Gmail Mobile
>
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
If you are on a Mac I strongly recommend source tree from attlasian. I
think is the better tool for git ever created. In windows I think smart git
is the option. My experience with egit was no so good.
El viernes, 10 de agosto de 2012, Michael A. Labriola escribió:
> >OK, but the first clone will be huge? I think our import file was in the
> 10's of GBs. I'm afraid to try to clone the flex project over my home
> network. I am testing by cloning the flex-site which worked from github.
>
> That is a big concern. I don't have a sense of how big it would be if all
> of the copies of files SVN has were made singular in the git method. We
> don't need to use github to figure it out though, we can make a local git
> repository and try this. I am willing to do so later next week when I
> should have time or, if someone else has time, they can do so first.
>
> Mike
>
>
>
--
Sent from Gmail Mobile
RE: What would it take to move to Git?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>OK, but the first clone will be huge? I think our import file was in the 10's of GBs. I'm afraid to try to clone the flex project over my home network. I am testing by cloning the flex-site which worked from github.
That is a big concern. I don't have a sense of how big it would be if all of the copies of files SVN has were made singular in the git method. We don't need to use github to figure it out though, we can make a local git repository and try this. I am willing to do so later next week when I should have time or, if someone else has time, they can do so first.
Mike
RE: What would it take to move to Git?
Posted by Gordon Smith <go...@adobe.com>.
Would we try to migrate the revision history from Subversion to Git?
- Gordon
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Friday, August 10, 2012 12:32 PM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
On 8/10/12 12:22 PM, "labriola@digitalprimates.net"
<la...@digitalprimates.net> wrote:
>
>> I am greatly concerned about disk space utilization if you have a
>> snapshot of everything including changes. Has anyone synced up with
>> Apache Flex Git since we stuffed it with Mustella tests? Will each
>> >branch/fork/clone we make actually replicate all of that data?
>
> Alex,
>
> Due to the way git stores files it is actually infinitely smaller than
> SVN storage over the long term, especially when one considers
> branches. If two files are the same, regardless if there are 7000
> branches, there is only a single copy of the file.
>
> If you are interested, here is some info on the overhead of git as
> perceived from the linux kernel project:
>
> https://git.wiki.kernel.org/index.php/GitBenchmarks#Repository_size_be
> nchmarks
>
> Mike
OK, but the first clone will be huge? I think our import file was in the 10's of GBs. I'm afraid to try to clone the flex project over my home network. I am testing by cloning the flex-site which worked from github.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/10/12 12:22 PM, "labriola@digitalprimates.net"
<la...@digitalprimates.net> wrote:
>
>> I am greatly concerned about disk space utilization if you have a snapshot of
>> everything including changes. Has anyone synced up with Apache Flex Git
>> since we stuffed it with Mustella tests? Will each >branch/fork/clone we
>> make actually replicate all of that data?
>
> Alex,
>
> Due to the way git stores files it is actually infinitely smaller than SVN
> storage over the long term, especially when one considers branches. If two
> files are the same, regardless if there are 7000 branches, there is only a
> single copy of the file.
>
> If you are interested, here is some info on the overhead of git as perceived
> from the linux kernel project:
>
> https://git.wiki.kernel.org/index.php/GitBenchmarks#Repository_size_benchmarks
>
> Mike
OK, but the first clone will be huge? I think our import file was in the
10's of GBs. I'm afraid to try to clone the flex project over my home
network. I am testing by cloning the flex-site which worked from github.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: What would it take to move to Git?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>I am greatly concerned about disk space utilization if you have a snapshot of everything including changes. Has anyone synced up with Apache Flex Git since we stuffed it with Mustella tests? Will each >branch/fork/clone we make actually replicate all of that data?
Alex,
Due to the way git stores files it is actually infinitely smaller than SVN storage over the long term, especially when one considers branches. If two files are the same, regardless if there are 7000 branches, there is only a single copy of the file.
If you are interested, here is some info on the overhead of git as perceived from the linux kernel project:
https://git.wiki.kernel.org/index.php/GitBenchmarks#Repository_size_benchmarks
Mike
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Friday, August 10, 2012, Alex Harui wrote:
>
>
> Anyway, I still am unable to find a way to clone from the Apache repo.
> GitHub seems to work, but I think that is read-only. If any committer can
> let me know how I can do that (and commit a test change) then I'll start a
> vote thread on moving to Git.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Maybe they forgot to give u permissions? Don't think u need perms to clone
tho, but maybe...
-omar
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/10/12 1:31 PM, "Carol Frampton" <cf...@adobe.com> wrote:
>
> don't think it works on a mac but SmartGit might be a possibility
>
SmartGit looks like SmartSVN. I think we are using it for commercial
purposes and will have to buy licenses.
Anyway, I still am unable to find a way to clone from the Apache repo.
GitHub seems to work, but I think that is read-only. If any committer can
let me know how I can do that (and commit a test change) then I'll start a
vote thread on moving to Git.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/10/12 4 :19PM, "Dasa Paddock" <dp...@esri.com> wrote:
>I've never used it but TortoiseGit is a port of TortoiseSVN that looks
>good for people who liked that:
>http://code.google.com/p/tortoisegit/
don't think it works on a mac but SmartGit might be a possibility
Carol
Re: What would it take to move to Git?
Posted by Dasa Paddock <dp...@esri.com>.
I've never used it but TortoiseGit is a port of TortoiseSVN that looks good for people who liked that:
http://code.google.com/p/tortoisegit/
On Aug 10, 2012, at 12:54 PM, Om wrote:
>>
>> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>>
> hoping GitHub for Mac would be the equivalent, but not so sure yet.
>>
>> The CLI seemed much more like SVN and worked for cloning from github, but I
>> am getting a timeout trying to clone from git.apache.org. Is it supposed
>> to
>> work?
>>
>>
> You may want to try SmartGit [1] then. It is developed by the same team.
> It is free for non-commercial use.
> In any case, any of the tools listed here should work fine [2]
>
> I havent used GitHub for Mac, I have no idea what the problem is. But it
> sounds like it is tied to the GitHub repo. It probably does not work with
> non github git repos.
>
> [1] http://www.syntevo.com/index.html
> [2] http://git-scm.com/downloads/guis
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
>
> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>
hoping GitHub for Mac would be the equivalent, but not so sure yet.
>
> The CLI seemed much more like SVN and worked for cloning from github, but I
> am getting a timeout trying to clone from git.apache.org. Is it supposed
> to
> work?
>
>
You may want to try SmartGit [1] then. It is developed by the same team.
It is free for non-commercial use.
In any case, any of the tools listed here should work fine [2]
I havent used GitHub for Mac, I have no idea what the problem is. But it
sounds like it is tied to the GitHub repo. It probably does not work with
non github git repos.
[1] http://www.syntevo.com/index.html
[2] http://git-scm.com/downloads/guis
Re: What would it take to move to Git?
Posted by Shannon Hicks <sh...@iotashan.com>.
SourceTree is a great free one.
Shan
Sent from my iPhone
On Aug 10, 2012, at 11:28 PM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>> hoping GitHub for Mac would be the equivalent, but not so sure yet.
> The github client probably a bit simpler. There are better graphical clients eg Tower out there but I don't know of any good free/OS ones.
>
>> The CLI seemed much more like SVN and worked for cloning from github, but I
>> am getting a timeout trying to clone from git.apache.org. Is it supposed to
>> work?
> Works fine for me, but took a little while (about 10 min) to clone the initial repo. Perhaps a firewall issue (git:// uses port 9418)?
>
> Thanks,
> Justin
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I don't use FB other than for editing. I use SmartSVN for SVN. I was
> hoping GitHub for Mac would be the equivalent, but not so sure yet.
The github client probably a bit simpler. There are better graphical clients eg Tower out there but I don't know of any good free/OS ones.
> The CLI seemed much more like SVN and worked for cloning from github, but I
> am getting a timeout trying to clone from git.apache.org. Is it supposed to
> work?
Works fine for me, but took a little while (about 10 min) to clone the initial repo. Perhaps a firewall issue (git:// uses port 9418)?
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
> Alex:
>
>> I've spent the morning trying to use Git. I gave up and am now reading the
>> doc, because it is so different from SVN. I tried a GUI (GitHub for Mac)
>> but it seems tied to GitHub. I don't know how to redirect it to look at
>> git.apache.org. The GUI loves to show me commit records, but not the
>> files
>> themselves. So now I am trying to learn the CLI.
>>
>
> Please see [1] and [2]. It has instructions on setting up Git with Flash
> Builder and on how to get github projects into FB directly.
>
> [1] http://zoltanb.co.uk/how-to-setup-git-on-flash-builder-4-5/
> [2] http://zoltanb.co.uk/how-to-import-github-projects-into-flash-builder/
>
>
I don't use FB other than for editing. I use SmartSVN for SVN. I was
hoping GitHub for Mac would be the equivalent, but not so sure yet.
The CLI seemed much more like SVN and worked for cloning from github, but I
am getting a timeout trying to clone from git.apache.org. Is it supposed to
work?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: What would it take to move to Git?
Posted by Gordon Smith <go...@adobe.com>.
Given what Om and Michael say about the tooling, I no longer have any concerns about Git.
- Gordon
-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Friday, August 10, 2012 12:25 PM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
On Fri, Aug 10, 2012 at 12:12 PM, Gordon Smith <go...@adobe.com> wrote:
> I only know two... I've used Perforce and Subversion for 20 years. For
> me, the most important thing is ease of use, such as what visual tools
> it has and how it integrates with IDEs like Eclipse.
Here is a tutorial on getting the Egit plugin to work with Flash Builder [1]
> With Git, can you do an Eclipse refactoring without worrying about
> which files you need to check out?
Yes, you can.
> Do files have to be checked out at all before being edited?
No. You can just start editing any file and the plugin is smart enough to figure things out.
> If so, is there an Eclipse plugin to check them out?
See [1]
> How do I see what files I need to submit, and what changes I've made?
In Flash Builder or Eclipse:
Project - right click > Team > Synchronize Workspace. You can see "incoming", "outgoing" and "conflicts" (Very similar to the Perforce Eclipse plugin)
> If this is all done on the command line, I have no interest in
> returning to 1972.
>
>
When I started with Git, this is exactly what I thought. But of late, I have started loving Git Bash (the command line environment for Git) But, for almost every feature, the EGit plugin for Eclipse/Flash Builder has proven to be sufficient.
Alex:
> I've spent the morning trying to use Git. I gave up and am now
> reading the doc, because it is so different from SVN. I tried a GUI
> (GitHub for Mac) but it seems tied to GitHub. I don't know how to
> redirect it to look at git.apache.org. The GUI loves to show me
> commit records, but not the files themselves. So now I am trying to
> learn the CLI.
>
Please see [1] and [2]. It has instructions on setting up Git with Flash Builder and on how to get github projects into FB directly.
[1] http://zoltanb.co.uk/how-to-setup-git-on-flash-builder-4-5/
[2] http://zoltanb.co.uk/how-to-import-github-projects-into-flash-builder/
- Gordon
>
> -----Original Message-----
> From: Omar Gonzalez [mailto:omarg.developer@gmail.com]
> Sent: Friday, August 10, 2012 11:55 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: What would it take to move to Git?
>
> >
> > I'm guessing we are one of the larger projects at Apache in terms
> > of code size
>
>
> This is precisely why I think we should strongly consider moving to Git.
>
> I understand the apprehension some may have with learn "Yet Another
> SCM Control", but really? How many other SCM systems have you used
> besides SVN and maybe CVS? I'm sure its not all that many. The
> commands are not that difficult to learn. There's not that many. The
> concepts are similar, the tools are just better in Git.
>
> It's also not something that has to prevent work today. Moving to Git
> would require establishing workflow for how to work with it and
> documenting it so a transition can be made that doesn't impede
> everyone's current progress.
>
> The current Git fork is getting sync'd to our SVN already. I would be
> willing to take the lead and experiment with the Git repository by
> making a fork to play around with and define and document in
> Confluence all of the workflows for moving to it. Once that's done we
> can figure out when to make the actual move and set a date and make a
> transition. Work on SVN can continue the whole time.
>
> -omar
>
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
On Fri, Aug 10, 2012 at 12:12 PM, Gordon Smith <go...@adobe.com> wrote:
> I only know two... I've used Perforce and Subversion for 20 years. For me,
> the most important thing is ease of use, such as what visual tools it has
> and how it integrates with IDEs like Eclipse.
Here is a tutorial on getting the Egit plugin to work with Flash Builder [1]
> With Git, can you do an Eclipse refactoring without worrying about which
> files you need to check out?
Yes, you can.
> Do files have to be checked out at all before being edited?
No. You can just start editing any file and the plugin is smart enough to
figure things out.
> If so, is there an Eclipse plugin to check them out?
See [1]
> How do I see what files I need to submit, and what changes I've made?
In Flash Builder or Eclipse:
Project - right click > Team > Synchronize Workspace. You can see
"incoming", "outgoing" and "conflicts" (Very similar to the Perforce
Eclipse plugin)
> If this is all done on the command line, I have no interest in returning
> to 1972.
>
>
When I started with Git, this is exactly what I thought. But of late, I
have started loving Git Bash (the command line environment for Git) But,
for almost every feature, the EGit plugin for Eclipse/Flash Builder has
proven to be sufficient.
Alex:
> I've spent the morning trying to use Git. I gave up and am now reading the
> doc, because it is so different from SVN. I tried a GUI (GitHub for Mac)
> but it seems tied to GitHub. I don't know how to redirect it to look at
> git.apache.org. The GUI loves to show me commit records, but not the
> files
> themselves. So now I am trying to learn the CLI.
>
Please see [1] and [2]. It has instructions on setting up Git with Flash
Builder and on how to get github projects into FB directly.
[1] http://zoltanb.co.uk/how-to-setup-git-on-flash-builder-4-5/
[2] http://zoltanb.co.uk/how-to-import-github-projects-into-flash-builder/
- Gordon
>
> -----Original Message-----
> From: Omar Gonzalez [mailto:omarg.developer@gmail.com]
> Sent: Friday, August 10, 2012 11:55 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: What would it take to move to Git?
>
> >
> > I'm guessing we are one of the larger projects at Apache in terms of
> > code size
>
>
> This is precisely why I think we should strongly consider moving to Git.
>
> I understand the apprehension some may have with learn "Yet Another SCM
> Control", but really? How many other SCM systems have you used besides SVN
> and maybe CVS? I'm sure its not all that many. The commands are not that
> difficult to learn. There's not that many. The concepts are similar, the
> tools are just better in Git.
>
> It's also not something that has to prevent work today. Moving to Git
> would require establishing workflow for how to work with it and documenting
> it so a transition can be made that doesn't impede everyone's current
> progress.
>
> The current Git fork is getting sync'd to our SVN already. I would be
> willing to take the lead and experiment with the Git repository by making a
> fork to play around with and define and document in Confluence all of the
> workflows for moving to it. Once that's done we can figure out when to make
> the actual move and set a date and make a transition. Work on SVN can
> continue the whole time.
>
> -omar
>
RE: What would it take to move to Git?
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>I only know two... I've used Perforce and Subversion for 20 years. For me, the most important thing is ease of use, such as what visual tools it has and how it integrates with IDEs like Eclipse. With Git, can you do >an Eclipse refactoring without worrying about which files you need to check out? Do files have to be checked out at all before being edited? If so, is there an Eclipse plugin to check them out? How do I see what >files I need to submit, and what changes I've made? If this is all done on the command line, I have no interest in returning to 1972.
Gordon,
Honestly, I understand where you are at but without knowing git perhaps you could refrain from passing judgment on it?
Yes there are GUI tools, no, it's not at all like perforce. Yes, you can refactor much, much better than either of the other ones you mentioned. Yes, there are plugins.
Mike
RE: What would it take to move to Git?
Posted by Gordon Smith <go...@adobe.com>.
I only know two... I've used Perforce and Subversion for 20 years. For me, the most important thing is ease of use, such as what visual tools it has and how it integrates with IDEs like Eclipse. With Git, can you do an Eclipse refactoring without worrying about which files you need to check out? Do files have to be checked out at all before being edited? If so, is there an Eclipse plugin to check them out? How do I see what files I need to submit, and what changes I've made? If this is all done on the command line, I have no interest in returning to 1972.
- Gordon
-----Original Message-----
From: Omar Gonzalez [mailto:omarg.developer@gmail.com]
Sent: Friday, August 10, 2012 11:55 AM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
>
> I'm guessing we are one of the larger projects at Apache in terms of
> code size
This is precisely why I think we should strongly consider moving to Git.
I understand the apprehension some may have with learn "Yet Another SCM Control", but really? How many other SCM systems have you used besides SVN and maybe CVS? I'm sure its not all that many. The commands are not that difficult to learn. There's not that many. The concepts are similar, the tools are just better in Git.
It's also not something that has to prevent work today. Moving to Git would require establishing workflow for how to work with it and documenting it so a transition can be made that doesn't impede everyone's current progress.
The current Git fork is getting sync'd to our SVN already. I would be willing to take the lead and experiment with the Git repository by making a fork to play around with and define and document in Confluence all of the workflows for moving to it. Once that's done we can figure out when to make the actual move and set a date and make a transition. Work on SVN can continue the whole time.
-omar
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I've used many VCS system over the years, RCS, PVCS, CVS, SNV, Clearcase, Visual source safe and more recently Git and Mercurial.
Moving from Git from SVN is fairly easy but there's a few conceptual things that are very different. I'd say it's the equivalent from going from a file locking VCS to concurrent one. It's a bit scary at first but you get use to it and it works very well. But it did take a little while to me to get use to it and every now and then I still try to use it like SVN.
- Commits are done locally. Means it's very fast and you can make lots of small changes and document them well.
- Branches are more like tags. Branching is cheap and fast. Switching between branches is fast. You use branches a lot but generally (in my experience) these are local and not always shared.
- Merging is far less painful than SVN.
Tool support is generally good and on par with SVN but you do need to use the command line form time to time. Syncing branches can be a little tricky at first depending on how you are using it but that's no different to SVN. Git commands can be a bit more cryptic than SVN but perhaps that just because I've not used it as long.
I really like that commits are done locally ie you don't need internet access when working on the code and than it's easy to share work in progress with other developers without checking back into the main repository.
As it gives you more freedom than SVN getting the processes right may be more effort and I'm guessing different people use it in different ways more so than SVN.
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Om <bi...@gmail.com>.
On Fri, Aug 10, 2012 at 11:55 AM, Omar Gonzalez
<om...@gmail.com>wrote:
> >
> > I'm guessing we are one of the larger
> > projects at Apache in terms of code size
>
>
> This is precisely why I think we should strongly consider moving to Git.
>
> I understand the apprehension some may have with learn "Yet Another SCM
> Control", but really? How many other SCM systems have you used besides SVN
> and maybe CVS? I'm sure its not all that many. The commands are not that
> difficult to learn. There's not that many. The concepts are similar, the
> tools are just better in Git.
>
+1
"I don't want to learn yet another SCM tool" is not a strong argument
IMHO. Also, there are other committers who dont know SVN. If we chose
SVN, they will have to learn a new scm tool as well. We are all smart
enough to learn new tools/technologies to get things done.
>
> It's also not something that has to prevent work today. Moving to Git would
> require establishing workflow for how to work with it and documenting it so
> a transition can be made that doesn't impede everyone's current progress.
>
> The current Git fork is getting sync'd to our SVN already. I would be
> willing to take the lead and experiment with the Git repository by making a
> fork to play around with and define and document in Confluence all of the
> workflows for moving to it. Once that's done we can figure out when to make
> the actual move and set a date and make a transition. Work on SVN can
> continue the whole time.
>
I will be more than happy to help you with this effort.
Thanks,
Om
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/10/12 2 :55PM, "Omar Gonzalez" <om...@gmail.com> wrote:
>>
>> I'm guessing we are one of the larger
>> projects at Apache in terms of code size
>
>
>This is precisely why I think we should strongly consider moving to Git.
>
>I understand the apprehension some may have with learn "Yet Another SCM
>Control", but really? How many other SCM systems have you used besides SVN
>and maybe CVS? I'm sure its not all that many.
I can think of at least 4 that I've used extensively but I think it might
be 5. I'm sure I can figure a new one out.
I'm just tired of spending time arguing about this kind of stuff. In the
meantime very few people have made any contributions so maybe we are way
over-engineering what is actually needed. And unlike Gordon, I don't want
my access to source control to be thru FlashBuilder.
Carol
Re: What would it take to move to Git?
Posted by Alex Harui <ah...@adobe.com>.
On 8/10/12 11:55 AM, "Omar Gonzalez" <om...@gmail.com> wrote:
>>
>> I'm guessing we are one of the larger
>> projects at Apache in terms of code size
>
>
> This is precisely why I think we should strongly consider moving to Git.
>
> I understand the apprehension some may have with learn "Yet Another SCM
> Control", but really? How many other SCM systems have you used besides SVN
> and maybe CVS? I'm sure its not all that many. The commands are not that
> difficult to learn. There's not that many. The concepts are similar, the
> tools are just better in Git.
>
> It's also not something that has to prevent work today. Moving to Git would
> require establishing workflow for how to work with it and documenting it so
> a transition can be made that doesn't impede everyone's current progress.
>
> The current Git fork is getting sync'd to our SVN already. I would be
> willing to take the lead and experiment with the Git repository by making a
> fork to play around with and define and document in Confluence all of the
> workflows for moving to it. Once that's done we can figure out when to make
> the actual move and set a date and make a transition. Work on SVN can
> continue the whole time.
>
There's no guarantee the project will decide to move to Git, but if you can
show us how to get there that will probably help.
I've spent the morning trying to use Git. I gave up and am now reading the
doc, because it is so different from SVN. I tried a GUI (GitHub for Mac)
but it seems tied to GitHub. I don't know how to redirect it to look at
git.apache.org. The GUI loves to show me commit records, but not the files
themselves. So now I am trying to learn the CLI.
I am greatly concerned about disk space utilization if you have a snapshot
of everything including changes. Has anyone synced up with Apache Flex Git
since we stuffed it with Mustella tests? Will each branch/fork/clone we
make actually replicate all of that data?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
>
> I'm guessing we are one of the larger
> projects at Apache in terms of code size
This is precisely why I think we should strongly consider moving to Git.
I understand the apprehension some may have with learn "Yet Another SCM
Control", but really? How many other SCM systems have you used besides SVN
and maybe CVS? I'm sure its not all that many. The commands are not that
difficult to learn. There's not that many. The concepts are similar, the
tools are just better in Git.
It's also not something that has to prevent work today. Moving to Git would
require establishing workflow for how to work with it and documenting it so
a transition can be made that doesn't impede everyone's current progress.
The current Git fork is getting sync'd to our SVN already. I would be
willing to take the lead and experiment with the Git repository by making a
fork to play around with and define and document in Confluence all of the
workflows for moving to it. Once that's done we can figure out when to make
the actual move and set a date and make a transition. Work on SVN can
continue the whole time.
-omar
RE: What would it take to move to Git?
Posted by Jason Moore <Ja...@harksolutions.co.uk>.
+1 from me. The structure Carol outlined in the latter part with a
development trunk and stable branches is how I'm used to working with
SVN.
Jason :)
(Thank god I've manage to bypass the company legal footer - I think.)
-----Original Message-----
From: Carol Frampton [mailto:cframpto@adobe.com]
Sent: 10 August 2012 15:31
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
Personally I'd like to come up with a relatively simple scheme for
branching using SVN and then get to work, especially since Apache infra
still considers Git experimental. I'm guessing we are one of the larger
projects at Apache in terms of code size and I want us to be able to get
infra support. I know we've used their services quite a few times
already.
We've spent 8 months pushing existing code around and not making any
forward progress with Flex. I understand that some people prefer Git
but at this point everyone knows SVN to some level and not everyone
knows Git.
Assuming we will release from trunk, I don't think everyone working in
trunk can work, even aside from the stability issues. If we all worked
for the same company, and all signed up to get our features done by date
X so we could release on date Y it might be possible. In the Apache
model people work on things when they can, so there might be
features/components that aren't done when someone decides to do a
release.
I think Alex is proposing that we all work in the dev branch (aka
unstable) and when it is time to release we cherry pick changes to move
back to trunk and then release from trunk. We would not be merging on a
daily or even weekly basis but at release time (perhaps too corporate
but could also have base levels and merge then). I think Justin raises
some legitimate concerns about multiple changes being made to the same
file but I think we can come up with a solution for that. Perhaps
changes don't get even get committed to the dev branch until you think
they are worthy of release but there are other alternatives as well.
I think you could also flip this and do dev work in trunk and then
create a branch for the release that was based on the last release tag
and then you move changes from trunk over to the release branch.
I'm having a hard time following the Alex/Justin discussion but I have
read some misinformation about SVN in there. You can do an svn merge
and then if there are conflicts, go back and resolve those conflicts and
mark the files resolved with svn resolve. Then you svn commit the
results of the merge. You can also block merges with svn --record-only
merge.
Carol
Re: What would it take to move to Git?
Posted by Dave Fisher <da...@comcast.net>.
On Aug 10, 2012, at 10:22 AM, Gordon Smith wrote:
> After Falcon is donated I expect to be making lot of changes to complete its MXML support. I strongly prefer to be able to work in SVN and not to have to learn Yet Another Source Code Control System. Is the idea that SVN would stay the primary repository and Git might become any option for development branches?
That seems to be what is written on http://www.apache.org/dev/git.html
As suggested the status may have progressed. To check you can search the infrastructure-dev archives, or you can ask on IRC #asfinfra
(I feel exactly like you about git, but am about to be pulled into its world because that's how some people I work with roll.)
Regards,
Dave
>
> - Gordon
>
> -----Original Message-----
> From: Carol Frampton [mailto:cframpto@adobe.com]
> Sent: Friday, August 10, 2012 7:31 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: What would it take to move to Git?
>
>
>
> On 8/10/12 5 :00AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
>> We must take into account that low activity was due to donation and
>> create a first incubation SDK. In the next months more people should
>> come to the project as it helps to develop some patch, bug or modification.
>>
>> The infrastructure should support huge changes and must be set up
>> before those changes start to be developed. Changes to UIComponent,
>> HTML5 port, and so on are huge and must live with the actual evolution
>> of other minor things.
>>
>> So taking into account that there are aggresive modification plans in
>> mind, I think we should go with the best branching model and not the
>> simplest.
>> If
>> there was no plans, maybe the later will be best.
>>
>>
>>> Agreed, but considering the relatively low commit activity ATM (I'm
>> listed 7th at [1] with 32 commits since January, which have nothing to
>> do with Flex code for example)., I'm wondering if it would make more
>> sense to start with the *simplest* branching model as opposed to the
>> *best* one, for now. You might need the latter downstream, but probably
>> not right now.
>
>
> Personally I'd like to come up with a relatively simple scheme for branching using SVN and then get to work, especially since Apache infra still considers Git experimental. I'm guessing we are one of the larger projects at Apache in terms of code size and I want us to be able to get infra support. I know we've used their services quite a few times already.
>
> We've spent 8 months pushing existing code around and not making any forward progress with Flex. I understand that some people prefer Git but at this point everyone knows SVN to some level and not everyone knows Git.
>
> Assuming we will release from trunk, I don't think everyone working in trunk can work, even aside from the stability issues. If we all worked for the same company, and all signed up to get our features done by date X so we could release on date Y it might be possible. In the Apache model people work on things when they can, so there might be features/components that aren't done when someone decides to do a release.
>
> I think Alex is proposing that we all work in the dev branch (aka
> unstable) and when it is time to release we cherry pick changes to move back to trunk and then release from trunk. We would not be merging on a daily or even weekly basis but at release time (perhaps too corporate but could also have base levels and merge then). I think Justin raises some legitimate concerns about multiple changes being made to the same file but I think we can come up with a solution for that. Perhaps changes don't get even get committed to the dev branch until you think they are worthy of release but there are other alternatives as well.
>
> I think you could also flip this and do dev work in trunk and then create a branch for the release that was based on the last release tag and then you move changes from trunk over to the release branch.
>
> I'm having a hard time following the Alex/Justin discussion but I have read some misinformation about SVN in there. You can do an svn merge and then if there are conflicts, go back and resolve those conflicts and mark the files resolved with svn resolve. Then you svn commit the results of the merge. You can also block merges with svn --record-only merge.
>
> Carol
>
RE: What would it take to move to Git?
Posted by Gordon Smith <go...@adobe.com>.
After Falcon is donated I expect to be making lot of changes to complete its MXML support. I strongly prefer to be able to work in SVN and not to have to learn Yet Another Source Code Control System. Is the idea that SVN would stay the primary repository and Git might become any option for development branches?
- Gordon
-----Original Message-----
From: Carol Frampton [mailto:cframpto@adobe.com]
Sent: Friday, August 10, 2012 7:31 AM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
On 8/10/12 5 :00AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>We must take into account that low activity was due to donation and
>create a first incubation SDK. In the next months more people should
>come to the project as it helps to develop some patch, bug or modification.
>
>The infrastructure should support huge changes and must be set up
>before those changes start to be developed. Changes to UIComponent,
>HTML5 port, and so on are huge and must live with the actual evolution
>of other minor things.
>
>So taking into account that there are aggresive modification plans in
>mind, I think we should go with the best branching model and not the
>simplest.
>If
>there was no plans, maybe the later will be best.
>
>
>>Agreed, but considering the relatively low commit activity ATM (I'm
>listed 7th at [1] with 32 commits since January, which have nothing to
>do with Flex code for example)., I'm wondering if it would make more
>sense to start with the *simplest* branching model as opposed to the
>*best* one, for now. You might need the latter downstream, but probably
>not right now.
Personally I'd like to come up with a relatively simple scheme for branching using SVN and then get to work, especially since Apache infra still considers Git experimental. I'm guessing we are one of the larger projects at Apache in terms of code size and I want us to be able to get infra support. I know we've used their services quite a few times already.
We've spent 8 months pushing existing code around and not making any forward progress with Flex. I understand that some people prefer Git but at this point everyone knows SVN to some level and not everyone knows Git.
Assuming we will release from trunk, I don't think everyone working in trunk can work, even aside from the stability issues. If we all worked for the same company, and all signed up to get our features done by date X so we could release on date Y it might be possible. In the Apache model people work on things when they can, so there might be features/components that aren't done when someone decides to do a release.
I think Alex is proposing that we all work in the dev branch (aka
unstable) and when it is time to release we cherry pick changes to move back to trunk and then release from trunk. We would not be merging on a daily or even weekly basis but at release time (perhaps too corporate but could also have base levels and merge then). I think Justin raises some legitimate concerns about multiple changes being made to the same file but I think we can come up with a solution for that. Perhaps changes don't get even get committed to the dev branch until you think they are worthy of release but there are other alternatives as well.
I think you could also flip this and do dev work in trunk and then create a branch for the release that was based on the last release tag and then you move changes from trunk over to the release branch.
I'm having a hard time following the Alex/Justin discussion but I have read some misinformation about SVN in there. You can do an svn merge and then if there are conflicts, go back and resolve those conflicts and mark the files resolved with svn resolve. Then you svn commit the results of the merge. You can also block merges with svn --record-only merge.
Carol
Re: What would it take to move to Git?
Posted by Carol Frampton <cf...@adobe.com>.
On 8/10/12 5 :00AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>We must take into account that low activity was due to donation and create
>a first incubation SDK. In the next months more people should come to the
>project as it helps to develop some patch, bug or modification.
>
>The infrastructure should support huge changes and must be set up before
>those changes start to be developed. Changes to UIComponent, HTML5 port,
>and so on are huge and must live with the actual evolution of other minor
>things.
>
>So taking into account that there are aggresive modification plans in
>mind,
>I think we should go with the best branching model and not the simplest.
>If
>there was no plans, maybe the later will be best.
>
>
>>Agreed, but considering the relatively low commit activity ATM (I'm
>listed 7th at [1] with 32 commits since January, which have nothing to
>do with Flex code for example)., I'm wondering if it would make more
>sense to start with the *simplest* branching model as opposed to the
>*best* one, for now. You might need the latter downstream, but
>probably not right now.
Personally I'd like to come up with a relatively simple scheme for
branching using SVN and then get to work, especially since Apache infra
still considers Git experimental. I'm guessing we are one of the larger
projects at Apache in terms of code size and I want us to be able to get
infra support. I know we've used their services quite a few times already.
We've spent 8 months pushing existing code around and not making any
forward progress with Flex. I understand that some people prefer Git but
at this point everyone knows SVN to some level and not everyone knows Git.
Assuming we will release from trunk, I don't think everyone working in
trunk can work, even aside from the stability issues. If we all worked
for the same company, and all signed up to get our features done by date X
so we could release on date Y it might be possible. In the Apache model
people work on things when they can, so there might be features/components
that aren't done when someone decides to do a release.
I think Alex is proposing that we all work in the dev branch (aka
unstable) and when it is time to release we cherry pick changes to move
back to trunk and then release from trunk. We would not be merging on a
daily or even weekly basis but at release time (perhaps too corporate but
could also have base levels and merge then). I think Justin raises some
legitimate concerns about multiple changes being made to the same file but
I think we can come up with a solution for that. Perhaps changes don't get
even get committed to the dev branch until you think they are worthy of
release but there are other alternatives as well.
I think you could also flip this and do dev work in trunk and then create
a branch for the release that was based on the last release tag and then
you move changes from trunk over to the release branch.
I'm having a hard time following the Alex/Justin discussion but I have
read some misinformation about SVN in there. You can do an svn merge and
then if there are conflicts, go back and resolve those conflicts and mark
the files resolved with svn resolve. Then you svn commit the results of
the merge. You can also block merges with svn --record-only merge.
Carol
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
We must take into account that low activity was due to donation and create
a first incubation SDK. In the next months more people should come to the
project as it helps to develop some patch, bug or modification.
The infrastructure should support huge changes and must be set up before
those changes start to be developed. Changes to UIComponent, HTML5 port,
and so on are huge and must live with the actual evolution of other minor
things.
So taking into account that there are aggresive modification plans in mind,
I think we should go with the best branching model and not the simplest. If
there was no plans, maybe the later will be best.
>Agreed, but considering the relatively low commit activity ATM (I'm
listed 7th at [1] with 32 commits since January, which have nothing to
do with Flex code for example)., I'm wondering if it would make more
sense to start with the *simplest* branching model as opposed to the
*best* one, for now. You might need the latter downstream, but
probably not right now.
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 1:44 AM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:
> On Fri, Aug 10, 2012 at 10:30 AM, Omar Gonzalez
> <om...@gmail.com> wrote:
> > ...The issue, as I see it, is that the best branching model to follow
> works
> > best in Git because of the much improved manner in which it handles
> > branching, merging, and additional features that SVN does not have such
> as
> > Rebasing and easily adding multiple remote forks....
>
> Agreed, but considering the relatively low commit activity ATM (I'm
> listed 7th at [1] with 32 commits since January, which have nothing to
> do with Flex code for example)., I'm wondering if it would make more
> sense to start with the *simplest* branching model as opposed to the
> *best* one, for now. You might need the latter downstream, but
> probably not right now.
>
Well, I would rather go through a change in workflows once instead of
making a decision now that we know we are going to want to revisit later
down the line.
>
> OTOH, if people who are fluent in Git are willing to help make the
> switch happen, I won't stand in the way of course.
>
> -Bertrand
>
> [1]
> http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fflex
I would be willing to take a lead on this. I can write up thorough examples
of the git commands that a committer would use in order to go through the
entire workflow outlined by the Git Branching Model.
There's even free Git clients for Windows and Mac from GitHub that I can
use to make videos and instructions off of and everyone can at least start
with a common GUI that they don't have to pay for as a result of switching
to Git, for those that have not used it yet.
-omar
Re: What would it take to move to Git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Aug 10, 2012 at 10:30 AM, Omar Gonzalez
<om...@gmail.com> wrote:
> ...The issue, as I see it, is that the best branching model to follow works
> best in Git because of the much improved manner in which it handles
> branching, merging, and additional features that SVN does not have such as
> Rebasing and easily adding multiple remote forks....
Agreed, but considering the relatively low commit activity ATM (I'm
listed 7th at [1] with 32 commits since January, which have nothing to
do with Flex code for example)., I'm wondering if it would make more
sense to start with the *simplest* branching model as opposed to the
*best* one, for now. You might need the latter downstream, but
probably not right now.
OTOH, if people who are fluent in Git are willing to help make the
switch happen, I won't stand in the way of course.
-Bertrand
[1] http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fflex
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
>
>
>
> Let me add one BIG WARNING as a mentor: branches might be much easier
> to manage with Git, but if a move to Git is a way to avoid agreeing on
> how branches are managed, that won't help IMO. I would recommend
> sorting that problem (which is a community problem, not a technical
> one) in svn first before considering a move.
>
The issue, as I see it, is that the best branching model to follow works
best in Git because of the much improved manner in which it handles
branching, merging, and additional features that SVN does not have such as
Rebasing and easily adding multiple remote forks.
I think in the discussions we've had most would agree that if we moved to
Git it would be to use the Git Branching Model that has been passed around:
http://nvie.com/posts/a-successful-git-branching-model/
So, in my eyes, I believe this to be both a technical problem as well as a
community problem. I feel that because we are on SVN we do not have
available to use the best options to choose from, especially considering we
have a Git solution readily available.
I would be willing to help out to test the Git infrastructure as much as
possible and document how the process of working with it would go.
-omar
Re: What would it take to move to Git?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Fri, Aug 10, 2012 at 9:40 AM, Alex Harui <ah...@adobe.com> wrote:
> Would we be working off of github.com?...
github can be part of the equation, but the repository from which
releases are cut needs to be hosted at apache.org.
As Justin pointed out, those are the places to look at:
https://git-wip-us.apache.org/ (which points to
infrastructure-dev@apache.org for discussions) - which is about
projects using Git @apache.org as their main code repository, as
opposed to svn.
http://www.apache.org/dev/git.html which is about using Git mirrors,
which are already functional for Flex AFAIK (and can be easily setup
if not).
Several ASF projects are already using Git as their main repo, though
AFAIK that's still considered experimental by our infrastructure
group. Those folks have been asking projects who want to do that to
also supply skilled volunteers to help setup and test the ASF's Git
infrastructure.
Let me add one BIG WARNING as a mentor: branches might be much easier
to manage with Git, but if a move to Git is a way to avoid agreeing on
how branches are managed, that won't help IMO. I would recommend
sorting that problem (which is a community problem, not a technical
one) in svn first before considering a move.
-Bertrand
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Work on github would be a dream :)
2012/8/10 Alex Harui <ah...@adobe.com>
> Would we be working off of github.com?
>
> Who controls who has write-access?
>
> What else do we need to worry about?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
--
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
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
Here's an blog post that describes how you can pull changes from anyone's
Git fork:
http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/
-omar
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 1:17 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> > We actually have a mirror already, I requested it a while back :)
>
> Yep but you can't use it's you would normally github right ie no pull
> requests? And it's not a bidirectional mirror right?
>
> Justin
>
>
No, the way Apache Cordova is using it is they are working in Apache Git.
The GitHub repositories are mirrored from Apache Git one way.
When they get Pull Requests they discuss the commits from the contributor's
in the Pull Request. We can browse code here, ask why it doesn't have unit
tests or ask about changes etc. Once they're ready to integrate they do so
into Apache Git, which for us would be git://git.apache.org/flex.git
The way Git works you can add and remove remote forks, so you can add the
committer's fork. You can then create a local branch, I usually call mine
integration. I then fetch the commit from the remote fork into my
integration branch, run unit tests, make any fixes, and then merge to
whatever fork the change was intended for that I created my integration
branch from. It makes the workflow really nice.
-omar
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> We actually have a mirror already, I requested it a while back :)
Yep but you can't use it's you would normally github right ie no pull requests? And it's not a bidirectional mirror right?
Justin
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
We actually have a mirror already, I requested it a while back :)
https://github.com/apache/flex
We would just have to come to a consensus and figure out the workflows we'd
use, document them and move to using the Apache Git, which is: git://
git.apache.org/flex.git
I'd be willing to do the work of doing some writing on the branching model,
which would basically just summarize the Git Branching Model posting with a
link. But I'd also fix up the README file so it looks a lot nicer in the
GitHub repo: https://github.com/apache/flex
All committers should already have read/write to git://
git.apache.org/flex.git I believe.
-omar
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
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
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
There's actual 341 Apache Git repositories being mirrored to GitHub:
https://github.com/apache
-omar
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 1:07 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> As far as I'm aware we couldn't use github.
>
> There's some info here:
> http://www.apache.org/dev/git.html
>
> A couepl of Apache projects do use git as there main version control but I
> think there a reluctance to use it over SVN as it still a work in
> progress/in alpha/beta support:
> https://git-wip-us.apache.org
>
> If you look at the infrastructure mailing list there's been a couple of
> Git issues recently.
>
> Thanks,
> Justin
Apache Cordova is using it: https://github.com/apache/incubator-cordova-docs
We already have the same set up as them: https://github.com/apache/flex
-omar
Re: What would it take to move to Git?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Moreover...I can't see why Apache would put problems to use systems that
would be necessary to the right evolution of the project. Apache should
help with this kind of things and ease the switch, no put more barriers.
> Look at Apache Cordova's history, they are actively using it, they have
> several repositories they're already managing Pull Requests from Git. They
> are also in incubation.
>
> Can't be that hard.
>
> Plus, note the Checklist on the same link.
>
> -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
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 1:11 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> Note the "Big freacking note" at the top of this page:
> https://git-wip-us.apache.org/docs/switching-to-git.html
>
> Thanks,
> Justin
>
Look at Apache Cordova's history, they are actively using it, they have
several repositories they're already managing Pull Requests from Git. They
are also in incubation.
Can't be that hard.
Plus, note the Checklist on the same link.
-omar
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 1:11 AM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> Note the "Big freacking note" at the top of this page:
> https://git-wip-us.apache.org/docs/switching-to-git.html
>
> Thanks,
> Justin
>
See here: https://github.com/apache/incubator-cordova-ios/pulls
They have lots of repos already, and they all have Pull Requests they're
handling, and they're still in incubation as well.
-omar
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Note the "Big freacking note" at the top of this page:
https://git-wip-us.apache.org/docs/switching-to-git.html
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
As far as I'm aware we couldn't use github.
There's some info here:
http://www.apache.org/dev/git.html
A couepl of Apache projects do use git as there main version control but I think there a reluctance to use it over SVN as it still a work in progress/in alpha/beta support:
https://git-wip-us.apache.org
If you look at the infrastructure mailing list there's been a couple of Git issues recently.
Thanks,
Justin
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
Apache Cordova is using Git:
https://github.com/apache/incubator-cordova-docs
It looks like they're using the Git mirror that is set up by Apache, and
they are managing Pull Requests via GitHub.
Apache is set up as an organization on GitHub, but it looks like they don't
have anyone actually added to the organization: https://github.com/apache
I also looked in one of their Pull Requests, and it doesn't look like they
have admin rights to the PRs because they're asking someone to CLose the
issue for them because they've already cherry picked their commit and
committed to the Apache Git which should appear in the GitHub mirror
shortly: https://github.com/apache/incubator-cordova-docs/pull/23
Looking at other tickets (
https://github.com/apache/incubator-cordova-docs/pull/26), they're creating
JIRA issues to track Pull Requests that come into GitHub and then they ask
the PR submitter to close it when its been integrated into the Apache Git.
Not ideal, but at least we can use GitHub's Pull Request code commenting
etc to interface with the community a lot easier than patches, as we can
comment on the commits in their forks.
-omar
Re: What would it take to move to Git?
Posted by Omar Gonzalez <om...@gmail.com>.
On Fri, Aug 10, 2012 at 12:40 AM, Alex Harui <ah...@adobe.com> wrote:
> Would we be working off of github.com?
>
> Who controls who has write-access?
>
> What else do we need to worry about?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
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