Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
June 11, 2007, 6:00 am
rate this thread
how to version your source code.
What I have always done is this:
major_build - I have never been involved with an application requiring a
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.
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.
Re: How to properly version your source code... ?
One of the best systems I've seen is "Major.Minor (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.Minor" 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