On Wed, Aug 27, 2008 at 09:52:36AM -0400, Matthias Julius wrote: > Carsten Möller <[EMAIL PROTECTED]> writes: > > > If it's stable, just svn-copy it to e.g. \tags\release01 > > It's just a pointer, not a physical copy, so don't worry. > > Maybe this should be anchored in the config file so > > one can decide whether he or she wants to render > > safely or test an experimantal version. > > Currently the client only does 'svn up' for its automatic updates. > This wouldn't be so simple with each new release being copied into a > new directory. It would then need to be told by the server how the > new release is called and do 'svn switch <new_release>'. > > Another approach could be to have the server tell clients to which rev > to update to and clients then do 'svn up -r<new_rev>'. This has the > disadvantage that it makes it impossible to apply a bug-fix to the > stable version.
It would be much simpler and cleaner to have a single stable directory that most clients check out, and the clients can then just run svn up. If you want to test a branch or anything you just "svn switch" to it. Yes, this requires merging, but at least with svk it really easy to do this. -- Knut Arne Bjørndal aka Bob Kåre [EMAIL PROTECTED] [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
