|
Just a couple of comments that may or may not play into your efforts:From a "disaster recovery" point of view, your company will now have two possible "points of failure" -- your System i machine is the first one, and the other is the Windows Server where you are running SubVersion hosting your SVN repository(s). Are the disks on that Windows server all mirrored or RAID-protected? So, instead of just simply running your nightly and weekly back-ups on i5/OS, you must also ensure that your SubVersion repositories are also backed-up. And, how will you ensure that those back-ups are "in sync" with each other? At least, with a SVN host running on i5/OS, even under PASE, when you run your full system back-ups (nightly and/or weekly), and include all the IFS directories, you will have backed up "everything" including your now precious SVN repositories, since this is now the "master" copy of all of your source code for your products. If you were to lose any of that stuff, as an ISV, this could cause serious harm (incurred costs, etc.) to your business.
1.) Personally we have abandoned the Softlanding SVN server port and
running SVN natively on the i. Speed is just not good enough for our
environment. The AIX one could be better but since we've already moved
our server to Windows, no reason to look back.
...(snip)...I do not consider it a "big deal" or worry about the date stamps in each source line. I am more concerned with the source file, library and member name and source last changed date/time stamps reflected in the OIR information of objects created from source, including: *PGMs, *MODULEs, *SRVPGMs (for binder source), *FILEs, *CLDs, *CMDs, *PNLGRPs, *QMFORMs, *QMQRYs, and *TBLs.
This may fly in the face of some of the comments I've read here in
regards to preserving line numbers and dates and object info, but from a
software vendor perspective it should work nicely to manage all of our
source projects using SVN. We are typically rebuilding our libraries for
each new release anyway so the only time the object info really matters
is when we build the product libraries.
More food for thought :-)
Regards,
Richard Schoen
...(snip)...
As an Amazon Associate we earn from qualifying purchases.
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.