Keeping revision history?

Oppie wrote:

I'm looking for recommendations for keeping the revision history as part

of a design file (ie what has changed in this revision/release).

 

Was considering adding a new sheet to the schematic or making a history

layer for text. Are there any ULPs or scripts that are geared toward

maintaining the revision history? Is there any good way to link to a

word document file which would be more user friendly for keeping a

history file?

 

Thanks in Advance,

Bob 'Oppie' Oppenheimer

I use tortoiseSVN:  www.subversion.tigris.org.  You can keep track of

all changes to your design file.  If necessary you can rollback to

previous versions if something goes wrong.  There is a little bit of a

learning curve but it's definitely worthwhile. Any other documents BOM,

test specs., etc. can also be place under revision control too.

Cheers,

Eagle User

Oppie wrote:

I'm looking for recommendations for keeping the revision history as part

of a design file (ie what has changed in this revision/release).

 

Was considering adding a new sheet to the schematic or making a history

layer for text. Are there any ULPs or scripts that are geared toward

maintaining the revision history? Is there any good way to link to a

word document file which would be more user friendly for keeping a

history file?

 

Thanks in Advance,

Bob 'Oppie' Oppenheimer

 

I use tortoiseSVN:  www.subversion.tigris.org.  You can keep track of

all changes to your design file.  If necessary you can rollback to

previous versions if something goes wrong.  There is a little bit of a

learning curve but it's definitely worthwhile. Any other documents BOM,

test specs., etc. can also be place under revision control too.

I fully agree that SVN is the way to go.  TortoiseSVN is a good Windows

client.  There are command line tools for linux that probably come with most

distributions.  I've recently started using RapidSVN that has clients for

Windows, Mac, and Linux so it's the same GUI in all three platforms.

Don't forget to backup the repository.

Cheers,

James.

-

 James Morrison  ~~~  Stratford Digital

 email:  sales2009@eaglecentral.ca

 fax:    888.701.8097

 web:    http://www.eaglecentral.ca

 Online EAGLE Dealer for US and Canada

 EAGLE Design Experts

 EAGLE Enterprise Toolkit

-

James Morrison wrote:

Oppie wrote:

I'm looking for recommendations for keeping the revision history as part

of a design file (ie what has changed in this revision/release).

 

Was considering adding a new sheet to the schematic or making a history

layer for text. Are there any ULPs or scripts that are geared toward

maintaining the revision history? Is there any good way to link to a

word document file which would be more user friendly for keeping a

history file?

 

Thanks in Advance,

Bob 'Oppie' Oppenheimer

I use tortoiseSVN:  www.subversion.tigris.org.  You can keep track of

all changes to your design file.  If necessary you can rollback to

previous versions if something goes wrong.  There is a little bit of a

learning curve but it's definitely worthwhile. Any other documents BOM,

test specs., etc. can also be place under revision control too.

 

I fully agree that SVN is the way to go.  TortoiseSVN is a good Windows

client.  There are command line tools for linux that probably come with most

distributions.  I've recently started using RapidSVN that has clients for

Windows, Mac, and Linux so it's the same GUI in all three platforms.

 

Don't forget to backup the repository.

 

Cheers,

 

James.

 

------------------------------------------

James Morrison  ~~~  Stratford Digital

 

email:  sales2009@eaglecentral.ca

fax:    888.701.8097

web:    http://www.eaglecentral.ca

 

Online EAGLE Dealer for US and Canada

EAGLE Design Experts

EAGLE Enterprise Toolkit

------------------------------------------

 

Didn't now about RapidSVN.  I'll have to take a look at it. Thanks for

the info.

Cheers,

Eagle User

Thanks EU

Was hoping to avoid another third party tool and keep the revision history

as part of the document. We have a small very limited field on the schematic

which gives the revision history. I wanted to make it include more

information about what changed since the last release.

I could also just reference an ECO in that limited field and then go to town

with as much information as needed in the ECO. Engineering change

documentation and management are part of our ISO9000 package that runs under

Lotus Notes. Guess I should look more deeply into this first.

Will download some of the SVN tools recommended and take a look.

Regards,

Oppie

"EAGLE user" <e4opening@yahoo.com> wrote in message

news:gkipsg$if0$1@cheetah.cadsoft.de...

Oppie wrote:

I'm looking for recommendations for keeping the revision history as part

of a design file (ie what has changed in this revision/release).

 

Was considering adding a new sheet to the schematic or making a history

layer for text. Are there any ULPs or scripts that are geared toward

maintaining the revision history? Is there any good way to link to a word

document file which would be more user friendly for keeping a history

file?

 

Thanks in Advance,

Bob 'Oppie' Oppenheimer

 

I use tortoiseSVN:  www.subversion.tigris.org.  You can keep track of all

changes to your design file.  If necessary you can rollback to previous

versions if something goes wrong.  There is a little bit of a learning

curve but it's definitely worthwhile. Any other documents BOM, test

specs., etc. can also be place under revision control too.

 

Cheers,

Eagle User

Hello Oppie,

I use SVN, it's great.  You can add a time stamp to a schematic by using

text, in Names layer type  >Last_Date_Time.  Click save and then redraw.

Regards,

Mike

"EAGLE user" <e4opening@yahoo.com> wrote in message

news:gkkf1k$c2p$1@cheetah.cadsoft.de...

James Morrison wrote:

Oppie wrote:

I'm looking for recommendations for keeping the revision history as

part

of a design file (ie what has changed in this revision/release).

 

Was considering adding a new sheet to the schematic or making a history

layer for text. Are there any ULPs or scripts that are geared toward

maintaining the revision history? Is there any good way to link to a

word document file which would be more user friendly for keeping a

history file?

 

Thanks in Advance,

Bob 'Oppie' Oppenheimer

I use tortoiseSVN:  www.subversion.tigris.org.  You can keep track of

all changes to your design file.  If necessary you can rollback to

previous versions if something goes wrong.  There is a little bit of a

learning curve but it's definitely worthwhile. Any other documents BOM,

test specs., etc. can also be place under revision control too.

 

I fully agree that SVN is the way to go.  TortoiseSVN is a good Windows

client.  There are command line tools for linux that probably come with

most

distributions.  I've recently started using RapidSVN that has clients for

Windows, Mac, and Linux so it's the same GUI in all three platforms.

 

Don't forget to backup the repository.

 

Cheers,

 

James.

 

------------------------------------------

James Morrison  ~~~  Stratford Digital

 

email:  sales2009@eaglecentral.ca

fax:    888.701.8097

web:    http://www.eaglecentral.ca

 

Online EAGLE Dealer for US and Canada

EAGLE Design Experts

EAGLE Enterprise Toolkit

------------------------------------------

 

Didn't now about RapidSVN.  I'll have to take a look at it. Thanks for the

info.

 

Cheers,

Eagle User