[mapguide-internals] Branch for MGOS 2.0

[Jason Birch]

Everyone can discuss it, and the PSC can rubber stamp it ;)

I'm thinking that users may be interested in building the released
version of MapGuide, rather than just the latest state of the branch
(with later fixes applied, etc).  As far as I can tell, there is no way
of doing this for 1.2.0.  Tagging doesn't cost anything, and I think
it's better to preserve the history than to regret not having done it
later.

Regardless of the specific tag used, I think it would be important to
have a consistent convention so that we don't end up with a
difficult-to-decipher directory listing like Boost's

http://svn.boost.org/svn/boost/tags/

I'm not entirely sure whether it's worth tagging RC and Beta releases.
If it is, I like Subversion's method:

http://svn.collab.net/repos/svn/tags/

Jason


-----Original Message-----
From: Trevor Wekel
Subject: RE: [MapGuide-internals] Branch for MGOS 2.0


So are you looking for something like
http://svn.osgeo.org/mapguide/tags/2.0.0 in Subversion?  Is this
something the PSC should discuss?