In terms of updates, the standard procedure is as follows for most of what our lab does.
#.0 - obviously a release version, for complete major changes. 0.# - An update of content. We usually start a project as 0.01 and go upwards to 99 if need be. If you think you will need a lot of small updates, you can use 0.001 as well. 0.0.# - A bug fix, for typos and such, with no new content added.
We also use prefix letters. A program that is in Alpha (closed testing) Will be build A1.09. Beta testing (open testing) is considered Build B1.09. Fairly helpful because the difference in Alpha is that you need to compile it yourself, Beta usually is precompiled itself.
In terms of updates, the standard procedure is as follows for most of what our lab does.
ReplyDelete#.0 - obviously a release version, for complete major changes.
0.# - An update of content. We usually start a project as 0.01 and go upwards to 99 if need be. If you think you will need a lot of small updates, you can use 0.001 as well.
0.0.# - A bug fix, for typos and such, with no new content added.
We also use prefix letters. A program that is in Alpha (closed testing) Will be build A1.09. Beta testing (open testing) is considered Build B1.09. Fairly helpful because the difference in Alpha is that you need to compile it yourself, Beta usually is precompiled itself.
Just thought I would add my two cents.
I'm going to be going up by 0.01 each update from now on.
Delete