The requirement to duplicate version numbers for hardware to software releases is an internal corporate decision, where the only relevance for compliance is that the character string used for the version number be identifiable and unique. Over the years MS, Apple, Cisco, etc have published software version numbering papers and some have even published internal corporate standards, but am not aware of any formal international standard. That is, code version numbering is whatever your company wants to do and how your internal libraries support parsing of version strings. These will get you started.
http://semver.org/ http://en.wikipedia.org/wiki/Software_versioning Brian -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Amund Westin Sent: Friday, November 09, 2012 12:04 AM To: [email protected] Subject: Revisions When making a HW change, the product top level revision number is stepping up. So, when a SW revision is introduced, how to avoid top level revision to be changed? SW revision is more likely than HW, and even SW update happens when product is placed on the marked (via GSM link) Any good ideas? #Amund - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
