I disagree. One key advantage of keeping community modules in subversion is continuous integration coverage. The -PallExtensions profile raises quality by forcing community modules to build or be kicked. This makes it a true incubator. Furthermore, it alerts core developers to community modules broken by core changes. These benefits are orthogonal to svn-vs-git debates.
Half of our team are using git-svn (Niels and I are the Linux developers). Until we get more feedback from Windows developers, we should exercise caution. Historically, git on Windows was not as strong. I love git, but I am not yet ready to force it on others. On 14/05/11 01:58, Gabriel Roldán wrote: > Hey, so this is my concern wrt community modules: IMHO the whole concept > of having community modules in the mainstream svn repo is obsolete. -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
