RE: Automate source code backup to SVN

[Adam Glauser <adamglauser@xxxxxxxxxxxx>]

Aaron Bartell wrote:

> I would only have three libraries [...] PROD, TEST, DEV.
>
> A developer would make all their changes in the DEV library (not their own
> library).  Each time they saved the member a SVN comitt would happen. 
> When they were done with their coding they would move the member to TEST
> at which point another trigger would happen that would submit that source
> to another
> SVN folder.  The same would happen when promoting to PROD.

Well, that seems like a pretty reasonable way to get started.  It buys you
the version history functionality that seems to be your main goal.  I'd
suggest that committing every single save to the DEV library might be a bit
excessive, but that just me.  I haven't used SVN enough yet to know whether
a really large number of commits could get unwieldy in practice.

The nice thing about your approach is that if you want to get some of the
other benefits of using SVN (like branching and tagging), it should be
fairly easy to modify or augment the process.  For example, as your team
gets more comfortable with SVN, you might each want your own working
directories instead of a single working directory.  This would allow two
people to collaborate on the same parts of the code at the same time more
easily, or try out different directions of development simultaneously.

Hope this is of some use,
Adam