How to properly version your 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.min or_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.

[Toby A Inkster]

Re: How to properly version your source code... ?

-Lost wrote:

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.

One of the best systems I've seen is "Major.Mino r (Build)".

"Build" is incremented automatically by the source repository software or
build system so that the developers never need to worry about it. The
"Major.Mino r" part is the publicly advertised version number incremented
whenever the marketing department feels like it.

--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.12-12mdksmp, up 107 days, 22:23.]

URLs in demiblog

http://tobyinkster.co.uk/blog/2007/05/31/demiblog-urls/

[Daniel W.]

Re: How to properly version your source code... ?

-Lost wrote:

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.min or_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.
>

Hi,

take a look at version control systems (like subversion
http://en.wikipedia.org/wiki/Subversion_%28software%29).

daniel

[Daniel W.]

Re: How to properly version your source code... ?

-Lost wrote:

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.min or_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.
>

Hi,

major and minor numbers and more are often used like you do.

Example for linux kernel...

http://www.linuxcertified.com/e-learning/linuxplus/html/1_9.html

(I think there exists a better description in the source folder...).

daniel