> Sure, you're making digital copies for DR (right? ... the only right answer is yes). Print paper of major revisions, put a copy in the fire safe and take a copy home (assuming that's not a license violation... if it is, send a copy home with a company officer).
For code preservation and data recovery, I have these rules:
- Developers each have a "local" RC repository on their primary network resource (that is, home drive on Windows, /home/$USER/net on our Linux systems). All WIP is checked into that repository for every change. (Changes are demarked when the dev runs a test).
- All changes are checked into site-daily RC at EoD.
- Any change must be eventually checked into the site-dev RC, but must pass all unit-tests first. Unit tests are run automatically on checked-in code.
- All repositories are backed up daily. (The normal corp. process takes care of having off-site copies and rotations)
- Daily/Weekly RC snapshots are backed up to DVD-RW, and encrypted to the VP and project manager's keys. One copy goes home with the VP weekly, and one goes home with the project manager daily.
Anything I appear to be missing?
radiantmatrix
require General::Disclaimer;
s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}