Revision control can be simple or complex. At the simple end of things:
At 12:04 PM 6/28/01 +1000, John Haddy wrote:
>All I do is clone the DDB as soon as a board's been sent for
>fabrication. All subsequent work (with one exception) happens
>on the new DDB.
>
>The exception is the "cleaning up" of the schematic part fields
>so that my BOM generation is correct - this usually gets done
>after the board's been sent to fab.
>
>Once this has been done, the DDB is made read-only at the Win2k
>level.
This is pretty basic.
What I do varies somewhat from client to client, but a simple system that I
like is that whenever I change a ddb and transmit it to the client, I
change a suffix. Preliminary ddbs, not fabbed, get letter suffixes, like
Project-A.ddb. ddbs released to fabrication get numbers, like
Project-1.ddb. While working on the next revision, I might add letters to
the number of the first revision, like Project-1A.ddb, which would become
Project-2 when released. I would often delete the letter suffix .ddbs after
a short while.
I don't lock the files, but where multiple designers are involved, it makes
sense to do so. There should never be a reason to go back and work on a
previous version, it should be left alone, to be copied if further work is
needed.
More sophisticated systems can involve a revision control officer who
issues drawing numbers and revision numbers, or this can just be a book
where new numbers are found and assigned. The point is to make sure that
.ddb names are unique.
Every document should have a single owner who has the right to change that
document. That owner can pass control, but there must be a clear procedure
for that. Assigning write access permissions would be one way to do that.
When I'm working on a design, it is important for me to be clear with the
engineer who it is who owns the schematic. If he thinks he owns it and I
think I own it, we may both make changes to it, and then one set or the
other of these changes will be lost or must be manually duplicated. It's a
very important point, I've seen a lot of wasted labor from unclarity on
this. If he owns it and I want to change it, I must send my requested
changes to him. Or vice-versa. Or we can pass ownership back and forth. But
it must be explicit. I haven't done it, but manipulating write permissions
might be one way to control this. The environment in which I presently work
does not need this level of control; we just tell each other who owns the
schematic. Generally, the one who draws the schematic owns it until control
is passed on.
What we don't want is for two people to take, say, Rev1A and each make a
Rev1B from it.
[EMAIL PROTECTED]
Abdulrahman Lomax
P.O. Box 690
El Verano, CA 95433
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
