How do you version your PCBs and schematics?

On 11/26/2012 02:54 PM, Matias Sjögren wrote:

Hi.

 

I just want to know how you decide versions on your PCBs and schematics.

 

For example:

1. You have a PCB version A and schematic version A and you just need to do a tiny fix(wich doesnt need anything in the schamatic to be changed) on the PCB wich will become version B.

 

2. You have a PCB version A and schematic version A, and then you have to change a component value(wich doesnt need anything in the PBC to be changed) in the schematic wich will become version B.

 

How do you handle versions on your PCB and schematic in these scenarios?

 

/Matias

 

Hi

I use git version control system and every changes is committed as in

your option 1. (stored as an restoring point), and every milestone (your

option 2.) is also tagged, which is basically a way of pinpointing

important happenings in your design.

You may then switch between different versions of your design with

simple commands whenever needed.

If you have never used version control software (VCS's) before, this can

be a bit hard to understand out of the blue (If you are familiar with

it, stop reading), but the simplest and "popular scientifically" way of

describing it is to call VCS a dynamic database that keeps track of your

file changes.

There is many VCS solutions and git is just one of them and which was

created by Linus Torvald, you know, the Linux guy. Then you have SVN and

CSV and many others. I find git very usable and handy for my eagle

designs. I also use it for keeping track of my library and the sw

projects +++.

This is helpful reading

http://git-scm.com/book/en/

Breg

Vidar (Z)

On 11/26/2012 02:54 PM, Matias Sjögren wrote:

Hi.

 

I just want to know how you decide versions on your PCBs and schematics.

 

For example:

1. You have a PCB version A and schematic version A and you just need to do a tiny fix(wich doesnt need anything in the schamatic to be changed) on the PCB wich will become version B.

 

2. You have a PCB version A and schematic version A, and then you have to change a component value(wich doesnt need anything in the PBC to be changed) in the schematic wich will become version B.

 

How do you handle versions on your PCB and schematic in these scenarios?

 

/Matias

 

Hi

I use git version control system and every changes is committed as in

your option 1. (stored as an restoring point), and every milestone (your

option 2.) is also tagged, which is basically a way of pinpointing

important happenings in your design.

You may then switch between different versions of your design with

simple commands whenever needed.

If you have never used version control software (VCS's) before, this can

be a bit hard to understand out of the blue (If you are familiar with

it, stop reading), but the simplest and "popular scientifically" way of

describing it is to call VCS a dynamic database that keeps track of your

file changes.

There is many VCS solutions and git is just one of them and which was

created by Linus Torvald, you know, the Linux guy. Then you have SVN and

CSV and many others. I find git very usable and handy for my eagle

designs. I also use it for keeping track of my library and the sw

projects +++.

This is helpful reading

http://git-scm.com/book/en/

Breg

Vidar (Z)