How to properly version source code... ?

[-Lost]

That pretty much sums it up. I am looking for information or tips on
how to version your source code.

What I have always done is this:

major_build.minor_build.daily_build

major_build - I have never been involved with an application requiring a
major build.

minor_build - When I have coded the application to the point of
warranting a release, or a new release.

daily_build - Anytime I add a new feature, fix a bug, or finish a TODO
item. I do not however increase this number if I add a TODO. I do
however add it to a HISTORY log.

I'd love to know what professional programmers and commercial software
engineers (as in, anyone who worked in a collaborative commercial
project where version information may have been set by the company) do.

Thanks.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

[anders]

On 11 Juni, 08:01, -Lost <[e-mail]:

That pretty much sums it up. I am looking for information or tips on
how to version your source code.

What I have always done is this:

major_build.minor_build.daily_build

major_build - I have never been involved with an application requiring a
major build.

minor_build - When I have coded the application to the point of
warranting a release, or a new release.

daily_build - Anytime I add a new feature, fix a bug, or finish a TODO
item. I do not however increase this number if I add a TODO. I do
however add it to a HISTORY log.

I'd love to know what professional programmers and commercial software
engineers (as in, anyone who worked in a collaborative commercial
project where version information may have been set by the company) do.

Thanks.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

In my company we use
Major, minor avn ev status

Major
Bigger changes, adding stuff that change produkt och adds nu way of
use it.

Minor,
relases buggrelase, new small fixes.
(Som fixes sends direct to customer and ev become a beta relase

Status
r<nfor relase ec r1 = First release
b<nbeta relase eg b1 = Beta no 1

Alpha and night builds never sends to customer so this don't have any
numbers.

// Anders

[C.W.Holeman II]

-Lost wrote:

What I have always done is this:

major_build.minor_build.daily_build

I'd love to know what professional programmers and commercial software
engineers (as in, anyone who worked in a collaborative commercial
project where version information may have been set by the company) do.

xx.yy-zz

xx: major changes that may require extra effort at install time.

yy: minor change to specification.

zz: no change in product specification, bug fixes. May include support
for new hardware but otherwise same feature set.

--
C.W.Holeman II | cw***@Julian5Locals.com-5 http://JulianLocals.com/cwhii
To only a fraction of the human race does God give the privilege of
earning one's bread doing what one would have gladly pursued free, for
passion. I am very thankful. The Mythical Man-Month Epilogue/F.P.Brooks