SVN hosting: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(where to host new SVN)
 
(+release notes)
Line 27: Line 27:
* Trac advantages
* Trac advantages
** [http://trac.osgeo.org/gdal/timeline Timeline] and [http://trac.osgeo.org/gdal/roadmap roadmap] provided for semi-automated release management (milestones)
** [http://trac.osgeo.org/gdal/timeline Timeline] and [http://trac.osgeo.org/gdal/roadmap roadmap] provided for semi-automated release management (milestones)
** Source browser integrated
** Auto-generation of release notes ([http://trac.osgeo.org/gdal/wiki/Release/1.4.1 GDAL example]) which we currently do by hand for thousands of fixes
** Source code browser integrated
** Wiki integrated
** Wiki integrated
** tickets can moved around among OSGeo projects
** tickets can moved around among OSGeo projects

Revision as of 09:22, 12 September 2007

The goal is to move to SVN infrastructure for GRASS 7. The hosting of SVN needs to be discussed. A new repository has to be created in any case, despite its physical location.


SVN repository with GForge at Intevation

GRASS GForge Server: http://wald.intevation.org/tracker/?group_id=21

Pro:

  • continuity for GRASS

Contra:

  • GForge is not really accepted by GRASS developers, low usage (much lower than with old RT). Important developers are not even registered at all
  • GForge is not integrated with CVS, apparently also not with SVN
  • Wiki is yet on another server

SVN repository with Trac at OSGeo

OSGeo SVN/Trac Server: http://trac.osgeo.org/

GDAL SVN/Trac Server: http://trac.osgeo.org/gdal/

Pro:

  • Integrated infrastructure with other OSGeo projects (GDAL, ...)
  • SVN and Trac nicely integrated, also Wiki integrated
  • Trac shows patches/diffs in SVN (example)
  • login (signon) embedded in OSGeo LDAP: single signon for OSGeo infrastructure
  • Trac advantages
    • Timeline and roadmap provided for semi-automated release management (milestones)
    • Auto-generation of release notes (GDAL example) which we currently do by hand for thousands of fixes
    • Source code browser integrated
    • Wiki integrated
    • tickets can moved around among OSGeo projects
    • easy ticket monitoring and retrieval
    • nice layout
  • potential new translation portal of OSGeo would integrate, too

Contra:

  • some time already invested in Intevation's GForge