BTW - there is no syntax. If you are producing a software, adopt any scheme that feels logical to you. You can always have your versioning upgraded if something will feel more right to you at later time.
Don't forget to upgrade versioning version also :)
Every organization makes up their own meanings for version numbers. You have to check their documentation if you want to be sure what they mean as far as compatibility and such.
发布评论
评论（3）
我为你搜索了它：我输入了“版本控制”，我得到的第一个链接是：
http://en.wikipedia .org/wiki/Software_versioning
HTH
顺便说一句 - 没有语法。如果您正在开发软件，请采用您认为合乎逻辑的任何方案。如果您以后感觉更合适，您可以随时升级版本控制。
不要忘记升级版本控制版本:)
I googled it for you: I typed 'versioning' and first link I got was:
http://en.wikipedia.org/wiki/Software_versioning
HTH
BTW - there is no syntax. If you are producing a software, adopt any scheme that feels logical to you. You can always have your versioning upgraded if something will feel more right to you at later time.
Don't forget to upgrade versioning version also :)
每个组织都有自己的版本号含义。如果您想确定它们在兼容性等方面的含义，则必须检查它们的文档。
Every organization makes up their own meanings for version numbers. You have to check their documentation if you want to be sure what they mean as far as compatibility and such.
程序集版本控制是主观的，基于个人/项目决定使用的约定。
但通常情况下，它与发布周期、错误修复和正在实施的新功能有关。
相关的SO问题提供了关于程序集编号含义的良好解释（详细信息在问题中，而不是答案中）
Assembly versioning is subjective based on the conventions a person/project decides to use.
Typically though, it is related to release cycles, bug fixes and new features being implemented.
A related SO question provides a good explanation regarding what the assembly numbering means (The detail is in the question, not the answer)