Application Version standard??
-
Is there a standard most programmers try to follow when assigning a version to their applications? For instance... I notice a lot of "newer" applications use a 4 digit field separated by commas. If this is a "standard", what is the meaning of each of the fields? I poked around a bit this morning, but haven't found anything yet. Before I get too carried away in a 2 or 3 hour search, I usually post a question here, as this forum has been an amazing resource for me. Thanks in advance.
-
Is there a standard most programmers try to follow when assigning a version to their applications? For instance... I notice a lot of "newer" applications use a 4 digit field separated by commas. If this is a "standard", what is the meaning of each of the fields? I poked around a bit this morning, but haven't found anything yet. Before I get too carried away in a 2 or 3 hour search, I usually post a question here, as this forum has been an amazing resource for me. Thanks in advance.
It's a goog question and it have been discussed a few times, here on CP, over the years. I guess people just do it as they want to. As far as I remember most people agree'd that the first is major version, and the second is minor version and the last is build. The third I cant remember... Like 1.2.0.77 version 1.2 build 77 - Anders Money talks, but all mine ever says is "Goodbye!"
-
Is there a standard most programmers try to follow when assigning a version to their applications? For instance... I notice a lot of "newer" applications use a 4 digit field separated by commas. If this is a "standard", what is the meaning of each of the fields? I poked around a bit this morning, but haven't found anything yet. Before I get too carried away in a 2 or 3 hour search, I usually post a question here, as this forum has been an amazing resource for me. Thanks in advance.
i don't know if there's a standard. but, i do it like this: A.B.C.D for applications: A = major revision. there's a good chance that most of the interface and/or internals will be new B = update . a new major feature has been added. this is the kind of feature that i would list on the product's web page. C = minor update . a minor feature was added. this might be just a new check box or option in a drop down somewhere. D = bug fix. -c
Image tools: ThumbNailer, Bobber, TIFFAssembler
-
Is there a standard most programmers try to follow when assigning a version to their applications? For instance... I notice a lot of "newer" applications use a 4 digit field separated by commas. If this is a "standard", what is the meaning of each of the fields? I poked around a bit this morning, but haven't found anything yet. Before I get too carried away in a 2 or 3 hour search, I usually post a question here, as this forum has been an amazing resource for me. Thanks in advance.
The linux kernel uses this standard: A.B.C.(D) A - Major revision number B - Minor revision number, where: Even numbers indicate "stable" releases Odd numbers indicate "development" or "beta" releases C - Major patch level D - Minor patch level This convention has been adopted by most of the linux community, and is used by many other developers as well. /moliate
The corners of my eyes catch hasty, bloodless motion - a mouse? Well, certainly a peripheral of some kind.
Neil Gaiman - Cold Colours
-
i don't know if there's a standard. but, i do it like this: A.B.C.D for applications: A = major revision. there's a good chance that most of the interface and/or internals will be new B = update . a new major feature has been added. this is the kind of feature that i would list on the product's web page. C = minor update . a minor feature was added. this might be just a new check box or option in a drop down somewhere. D = bug fix. -c
Image tools: ThumbNailer, Bobber, TIFFAssembler
thanx, i was also looking for the same stuff
-
i don't know if there's a standard. but, i do it like this: A.B.C.D for applications: A = major revision. there's a good chance that most of the interface and/or internals will be new B = update . a new major feature has been added. this is the kind of feature that i would list on the product's web page. C = minor update . a minor feature was added. this might be just a new check box or option in a drop down somewhere. D = bug fix. -c
Image tools: ThumbNailer, Bobber, TIFFAssembler
Thanks everyone, It looks like I've got my answer! no standard :) I suppose I might as well throw in my own usage. In the past I've only used three fields, and here's how they've been defined... Ver A.B.C Where A = Major "Generic"... a generic is a set of defined features. Not all features of a Generic have to be present in the initial release. B = A subset of the generic that pulls in more of the defined features. C = Bug Fixes Example... The initial release of a product would be 1.0.0, and might include 6 of 10 major features that are targeted for that Generic. 1.1.0 might include 8 of 10 features, and 1.2.0 all features. Along the way, you would have bug fix releases that would increment the third field. Just my two cents.