On the subject of revision control:
What do y'all use for revision control within Protel? At the moment we use a
"manual" method, whereby each board is contained within 3 folders - archive,
current, and experimental. It's left up to the designer/engineer to archive
old stuff, move experimental into current (once verified), and copy current
into experimental to make changes. Needless to say, this doesn't always
happen...
We have very short board life cycles (we're running a scientific experiment,
the immediate electronic needs of which change pretty much weekly), so I'd
like something that's more automated than what we use currently (especially
for those who are more interested in designing than any of that namby-pamby
revision control stuff - "what's that? the new board has an error? sorry, I
overwrote the old version with the new one". Don't laugh - this happens here
all the time...). We're lucky if a board lasts for six months in "current",
if that matters at all. Any ideas?
Cheers,
Matthew van de Werken
Electronics Engineer
CSIRO Exploration & Mining - Gravity Group
1 Technology Court - Pullenvale - Qld - 4069
ph: (07) 3327 4685 fax: (07) 3327 4455
email: [EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/subscrib.html
* - or email -
* mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Browse or Search previous postings:
* http://www.mail-archive.com/[email protected]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
