Version number conventions

[JPJeffery]

I was wondering, what is the convention or standard (de facto or otherwise) for version numbering scripts?

Or is it up to each individual programmer or company/dept.?

JJ
[small][purple]Variables won't. Constants aren't[/purple][/small]

 

[mrmovie]

i am sure there is a 'standard' somewhere which everyone is supposed to conform to....

Versions numbers for the Unicode Standard consist of three fields, denoting the major version, the minor version, and the update version, respectively. For example, "Unicode 3.1.1" indicates major version 3 of the Unicode Standard, minor version 1 of Unicode 3, and update version 1 of minor version Unicode 3.1.

 

[JPJeffery]

Well, in some ways that produces more questions.

Specifically, what do they define as a major version, or a minor version or an update?

I know what I define as Major/Minor/Update but is that the same as everyone else's definition? To me,

MAJOR
First version, or first LIVE version, or new version that either
i. Introduces new functionality AND/OR
ii. involves a major rewrite of the code that produces the existing functionality.

MINOR
New code to change how functionality is achieved or minor improvements.

UPDATES
Bug fixes or changes to file locations/names

And if I'm using, or letting people use, a not-quite-live version I'll precede the version number with b for Beta (e.g. vb1.01).

How do this match up with your practices?

JJ
[small][purple]Variables won't. Constants aren't[/purple][/small]

 

[58sniper]

I've used that same method for PHP scripting, and it's always served me well. There is surely some gray area about where the division is between them. But I think the above method is best.

I'm new to vbscripting, so I don't have anything past 1.1.0 yet!

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt