Re: Version Numbers

"Rob Horton" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> Hi,
> 
> the other day I was pondering my methodology for creating new version
> numbers for my embedded products.
> It is very simple and is in the form A.B where A represents a big change and
> B represents a small change.
> 
> I got to wondering if there is a standard for version numbers. Does anyone
> know of any?
> 
> As an example, in Delphi, the version number is of the form A.B.C.D where:
> 
> A = Major version
> B = Minor Version
> C = Release
> D = Build
> 
> So does that mean we can have different releases of the same version? But
> then surely a different release will be a different version?
> Should build be incremented each time a project is compiled?
> 
> (please note, this isn't a Delphi specific question. I only used delphi as
> an example.)
> 
> What sort of system do "you" use?

A = Major version: Incremented on requirements change; B and C are reset
B = Minor Version: Incremented on design change: C is reset
C = Release: Incremented on implementation change
D = Build: Continually increment, never reset