John Larkin
07-02-2003, 07:18 AM
On 2 Jul 2003 04:21:36 -0700, H_shemisone@yahoo.com (Yaakov) wrote:
Are people using formal Version Control systems for embeddedapplications? If you're using something other than a nightly backup tothe network server, I'd like to know what it is. Might want toformalize something where I workTIA,Yaakov
We do casual backup to a server, which is CD-Rom backed up every
Friday for permanent archiving (in the cave under my garage.)
Version control is different: when a firmware version is "done", it is
formally packaged on a Zip or CD: all sources, batch files, related
FPGA config files, ROM image files, and a serious README.TXT
explaining the whole thing. All that is formally released to the
company library as a letter revision, treated exactly like an
engineering drawing... none of this silly 7.04b nonsense.
Manufacturing may only assemble a product from released drawings, as
called out on a released BOM. The master Zip or CD then goes into the
cave, too.
We also archive the tools (assemblers, compilers, FPGA stuff, etc)
used to produce any released firmware. That has prevented a few
near-nightmares in maintaining "old" (2 years or so) products.
John
Are people using formal Version Control systems for embeddedapplications? If you're using something other than a nightly backup tothe network server, I'd like to know what it is. Might want toformalize something where I workTIA,Yaakov
We do casual backup to a server, which is CD-Rom backed up every
Friday for permanent archiving (in the cave under my garage.)
Version control is different: when a firmware version is "done", it is
formally packaged on a Zip or CD: all sources, batch files, related
FPGA config files, ROM image files, and a serious README.TXT
explaining the whole thing. All that is formally released to the
company library as a letter revision, treated exactly like an
engineering drawing... none of this silly 7.04b nonsense.
Manufacturing may only assemble a product from released drawings, as
called out on a released BOM. The master Zip or CD then goes into the
cave, too.
We also archive the tools (assemblers, compilers, FPGA stuff, etc)
used to produce any released firmware. That has prevented a few
near-nightmares in maintaining "old" (2 years or so) products.
John