On Sat, Dec 11, 2010 at 10:20 PM, Owen Winkler <[email protected]> wrote: > Git also offers the traditional advantages of distributed SCM, in that I > could work on a feature to completion locally with the benefit of local SCM, > and when the feature was complete enough, could push it to the central repo > where everyone else could use it. The advantage is that features added by > single developers that aren't ready for distribution wouldn't be introduced > to everyone in their incomplete state, but those developers would be able to > maintain their own versioning locally on their work. This is not possible > with svn alone.
I was under the impression that we specifically wanted to discourage this kind of isolated development. I thought the whole point of using SVN branches was to allow folks to work on new, potentially broken stuff in a visible, open-to-the-community fashion, so that other developers could lend a hand, or at least keep an eye on the goings-on. Whether this kind of transparent feature development methodology ever worked for us may be another matter. I think Git's benefit you described above would lead to a lot more isolated, opaque developments. Moreover, it could result in duplication of effort as people work independently and unaware of similar efforts from others. An atomic check in of a big new feature seems to go against many of the discussions we've had on this mailing list in the past. Cheers, Scott -- 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/habari-dev
