I am currently in a bureaucratic hell with my company and I need to determine what the various software levels for our test programs are. We have a rough practice that we follow ourselves, but I am looking for a standard (if one exists) for reference in our quality system. I admit that systems can vary widely between developers, but in the end I'm looking for a “best practice” guide that represents a major change, minor changes, etc. I would like to refer to the published document in my submission to our quality system for ISO, if possible.
To make it clear that the software developed by my company is used internally to automate the testing of Semi-Conductors. We do not sell this code, and version control is for accounting purposes only. We use xyz changes to provide the level of statement and approval required for release.
It’s good practice to use level 3 fix numbers:
xyz
x is the primary y is the minor z - bug fixes
, x . y , , x , . . , , z , .
:
x.y.z:
x.y.z.build
x =y =z =build =
, , , .
, @lewap,
x.y.z
z , .
y UI/API ,
x - / (.. Oracle SQLServer) - , , , "",
, , ().
. , - .
x.y x.y.z . Z R & D , ( - Scrum ).
, , . .
, , , , - .
, , , major.minor . , UNIX ( ), .
major.minor, , , , . Windows 2,0 3.0 - 2,0 Windows 3,0. () - WP & n .
- , . Windows 2.0 3.0 . -, .
A , chanhe, , . , Win 3.0 Win 3.1 , .
, , . , GNU ++ 3.4.5 - 3.4.4 - !
: . , . . , :
Peter van den Hamer Kees Lepoeter (1996) : , , IEEE, . 84, № 1, 1996 .