Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!news-out.netnews.com!postmaster.netnews.com!us1.netnews.com!not-for-mail
X-Trace: DXC=4elWXK5Gaf>XbTXBL>DDB=U5[F2hIijD?7J470dMQQ7;AUDUcSnb?@9Yc1gZ:k^?G>>Zm?6_:X_2<gGD7EYch9n2Uh:ZAVm]2i41NI1l8fb?f>XlnNGcjcaF4
X-Complaints-To: support@frugalusenet.com
Date: Mon, 24 Mar 2025 14:14:38 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Newsgroups: sci.electronics.design
Content-Language: en-US
From: bitrex <user@example.net>
Subject: PCB version control
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 11
Message-ID: <67e1a08c$0$3831$882e4bbb@reader.netnews.com>
NNTP-Posting-Host: 127.0.0.1
X-Trace: 1742839948 reader.netnews.com 3831 127.0.0.1:40645

How do you version control your PCBs these days?

I'm at the point I need to implement a more consistent schema for 
hardware versions, prototype, and production boards.

E.g. PCB-12345-R-B where 12345 is the PCB/product identifier and B is 
the manufacturing revision. Would you letter designate prototypes that 
are manufactured as well, or just revisions intended for public 
consumption?