L
-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.
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.