OWEN.DAVID
Member
I am interested in good examples and best practices when choosing a project file name.
Would you expect to include all or some of the following,
* site/machine name
* last revision date
* version number
* programmer name / credentials
* firmware version
* work order number
* anything else??
I'd be keen to hear what has worked for everyone else or if there is an accepted standard for project file names.
Otherwise, I have been keeping a log of changes to the program using rung comments in a routine full of NOP instructions.
Is this the best way to add more verbose information to a project file to track dates and details of changes? Is the preference to keep this info. in the program or an external release notes document?
Interested to hear what works for everyone.
Thanks!
Would you expect to include all or some of the following,
* site/machine name
* last revision date
* version number
* programmer name / credentials
* firmware version
* work order number
* anything else??
I'd be keen to hear what has worked for everyone else or if there is an accepted standard for project file names.
Otherwise, I have been keeping a log of changes to the program using rung comments in a routine full of NOP instructions.
Is this the best way to add more verbose information to a project file to track dates and details of changes? Is the preference to keep this info. in the program or an external release notes document?
Interested to hear what works for everyone.
Thanks!