Quote:
Originally Posted by tompe
Or they do not work so much...
I like to check in each change but it is common to have a policy that you only check in things that build cleanly. So if you have this policy the number is not unreasonable especially if you only have on project in the repository.
|
Or devs can only check in changes that don't break the build also. We have about 6 devs working on our trunk and 4 branch versions. We do a CI build on each check in and that is our "build" number. But, we reset the build number to 0 on each Major or Minor version change. Not on hotfix or service pack versions though.
BOb