> You asked technology questions, and received technology answers. > Surprising?.
Not. I'm surprising that exists so "narrowed" view of the problem. > Distributed version control is much better suited for a project which has > the > magnitude of Android, where a lot of different partners want to have their > own repositories with a crazy number of branches and custom modifications. > > If you think that a single SVN server can handle that, you're mistaken. If > you > think that this can be managed by having several SVN repositories (e.g. a > public > one and various 'internal' ones), you don't know the nightmare that properly > synchronizing them can be at times (e.g. repeated merge conflicts) Not exactly true. Any big enough vendor will work on internal environment which much better controlled, tested and etc. That means that any vendor will have a problem of creating own repository copy on own servers. > Maybe, maybe not, but nothing says these must be "Windows-exclusive > developers". Look like you are afraid of competitors on Android market :) Too many innovative technologies developed on windows os. And open source can be everywhere. At the current moment Android development request for developers with high experience, and they cost a lot, so initial cost of the Android development is still high. Make it lower and many good things appears there. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
