This is the "soon-to-be" layout suggested by moi, daxxar, ;-)
I'd like everyone to take a look at this, and append any (constructive)
comments to the end of this file.

/trunk/     -- Current "source", add new features and fix bugs
/trunk_vX/  -- Source for version X, merge bugfixes from /trunk/ to here.
               (Use a svn cp (with two urls for cheap copy) 
                 to "branch" it when /trunk is ready)
/branches/  -- Large modifications of source should get a cheap copy of here
               before they are started, if you expect it to (temporarily)
               break source usability.
/tags/      -- All releases should be copied here, major and minor releases.
               (i.e. v1, v1.01, v1.02, v1.1, v1.11, v1.12 etc)
/other/     -- random stuff that's doesn't need to abide to pzs-ng svn layout
               (i.e. not directly related to pzs-ng)


On the note of tags; we should decide on a versioning policy.
Will we have v1, v2, v3, where v1.1, v1.2 are bugfixes, or do we use v1.0, v1.1, v1.2,
where v1.01, v1.02, etc. are bugfixes? IMHO we should use v1, v1.1, etc.


-- daxxar.


Since "/trunk_vX/" in the example above is a real branch I suggest keeping it 
under /branches/ to keep the root dir free from pollution and to prevent 
confusion.

-- dakrer


I happen to agree with dakrer - vX should be under branches/.
As for versioning - it's a bit early to tell. If only bugs are fixed, minor
versioning should be used (ie, v1.01). If we do features, a normal versioning
should be used (ie, v1.1). If we rewrite stuff, making old versions incompatible
or do some major work, major versioning should be used (ie 2.0).


-- psxc