Re: Subversion

> It sounds similar to continuus, a commercial system I have used. Each
> developer had their own project instance. 

It isn't.  What you are describing is how client state is managed.
In systems like Perforce, ClearCase and this one you mention, the
server tries to keep track of client state.  Roughly speaking it
knows what you have checked out (in the CVS sense of the term)
and where on your client filesystem.  That approach can give
good performance since most developers haven't modified most
of the files.  Subversion gets the client to keep track of its
own state.  The client keeps a lot of information locally to
make it more efficient.  For example pristine copies of the files
are kept, so the 'svn diff' operation is performed locally.

What I have been describing the prior email is the policy for
branching and tagging naming.  Read the svn book.

> I've been doing test versions by incrementing the "testver" in version.py.

We will be able to use the revision number instead and get that
for free.

> Can you recommend any reading that shows how I would go about making these
> available for download?
> Can I do this with the developer role?

How many people are you giving these builds to?  The file release
system is really nasty to deal with.

If it is just one or two people then it will be way easier just to
email them the builds.  If they can't accept large emails then
they can get gmail accounts.  (I have plenty of invites.)

Roger


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642