× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'd suggest that committing every single save to the DEV library might be
a bit excessive, but that just me.

Good point. Sounds like another config file option (commit frequency).
Could probably have it configured to do "every save", "every 1/2 day", and
"every day". The latter two could be Job Scheduled Entries.

Hope this is of some use...

Yes! Yes it is. If any other thoughts come up please let me know. This
will be a good Christmas vacation project, so maybe I will have something by
the first of the year.

Thanks,
Aaron Bartell
http://mowyourlawn.com

BTW, rockin' out to http://www.purevolume.com/untiljune (listen to
"Sleepless")


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Wednesday, November 28, 2007 9:14 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Automate source code backup to SVN

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.