Another benefit of keeping community modules in a central repo is that it keeps them open for public scrutiny, comment, and involvement, even when they are a work-in-progress. In my view, this increases openness and transparency. Even prototype modules can have unexpected new users come out of the woodwork. I think these benefits would be reduced if works-in-progress were moved to other repos.
On 16/05/11 10:35, Ben Caradoc-Davies wrote: > 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. -- 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
