[Schevo-devel] Repository restructure

[Matthew Scott]

In order to make branch-based development [1] happen more smoothly,  
we've inverted the location of trunk, branches, and tags.

Rather than each project (Schevo, SchevoGtk, SchevoXml, etc.) have  
its own set of branches, tags, and trunk directories, those are now  
at the top level of the repository, and each project is contained  
therein.

If you're tracking Schevo trunk, use the top-level trunk URL [2]:

   svn co svn://orbtech.com/schevo/trunk schevo

After checkout is complete, you'll have a 'schevo' directory.  It  
will contain Schevo itself as well as each optional package (minus  
the 'Schevo' prefix, in order for tab completion to work well).

Go into the directories for the packages you need and run "python  
setup.py develop" just as you would before.

There are four branches in progress, that more or less mirror the  
branches in the previous directory structure:

tabula-rasa: adds the SchevoGtk package as "Gtk"

metaschema-draft: adds the SchevoMetaschema package as "Metaschema"

timezone: modifies the Schevo package to support timezones in  
datetime fields

no-namespace-packages: modifies the package names to no longer use  
namespace packages.  (For instance, 'schevo.xml' will become  
'schevoxml')

Hopefully, this new structure will make branches easier to maintain  
for changes that span multiple packages, and will make the review and  
merge process faster and more fluid.


[1] Divmod's renamed their branch based development page -- they're  
now calling it http://divmod.org/trac/wiki/ 
UltimateQualityDevelopmentSystem -- and it's still a good resource to  
re-read on occasion.

[2] Pat O'Brien is in the process of provisioning a new server that  
will give us faster Subversion service as well as a Trac setup.  The  
Subversion URLs will change again when it is ready, but the directory  
structure will not.

--
Matthew Scott
mscott at springfieldtech.com