Is there a standard practice For Version Control

[jyoung2]

I have been looking for an article explaining the Standards of using version control. I understand the point of Major builds but when should a Minor build be incrementeted and what is the difference between a build and a revision.

Sorry if this seems simple but I am mostly self taught starting with Access and just recently switching to .net and I am trying to start good habits from the begining.

Thank you for the Help

[Curtis Rutland]

Since this isn't specific to .NET, I'm moving this to the "Software Development" forum.

[RedSon]

I have been looking for an article explaining the Standards of using version control. I understand the point of Major builds but when should a Minor build be incrementeted and what is the difference between a build and a revision.

Sorry if this seems simple but I am mostly self taught starting with Access and just recently switching to .net and I am trying to start good habits from the begining.

Thank you for the Help

There is no set standard for version control. There is a popular nomenclature that companies use that they take from Microsoft. Basically you should increment the minor version number any time you want to make a new supported release. And you increment a major version any time the has been feature changes to your application.

For a good synopsis of versioning you can check out mozilla's projects like firefox and read the changelogs. You can see what their reasons were behind the version numbers.

[jyoung2]

Thank you for the input, I will take a look