问题描述
是否有任何指南或标准的最佳实践如何为您在业余时间开发的软件版本化以获取乐趣，但仍然会被某些人使用?我认为有必要对此类软件进行版本控制，以便您了解第 1 版所讨论的内容(例如用于错误修复、支持等).
Is there any guideline or standard best practice how to version a software you develop in your spare time for fun, but nevertheless will be used by some people? I think it's necessary to version such software so that you know about with version one is talking about (e.g. for bug fixing, support, and so on).
但是我从哪里开始版本控制?0.0.0?还是0.0?然后如何增加数字?大版本.小改动?对版本控制系统的任何承诺不应该是另一个版本吗?还是仅适用于以高效方式使用的版本?
But where do I start the versioning? 0.0.0? or 0.0? And then how to I increment the numbers? major release.minor change? and shouldn't any commit to a version control system be another version? or is this only for versions which are used in a productive manner?
推荐答案
你应该从版本 1 开始，除非你知道你发布"的第一个版本在某种程度上是不完整的.
You should start with version 1, unless you know that the first version you "release" is incomplete in some way.
至于如何增加版本，这取决于您，但请使用主要、次要和内部版本编号作为指导.
As to how you increment the versions, that's up to you, but use the major, minor, build numbering as a guide.
没有必要将您提交给源代码管理的每个版本都作为另一个版本——您很快就会拥有一个非常大的版本号.您只需要在向外界发布新版本时(以某种方式)增加版本号即可.
It's not necessary to have every version you commit to source control as another version - you'll soon have a very large version number indeed. You only need to increment the version number (in some way) when you release a new version to the outside world.
因此，如果您从 1.0.0.0 版到 2.0.0.0 版进行了重大更改(例如，您从 WinForms 更改为 WPF).如果您进行较小的更改，请从 1.0.0.0 移动到 1.1.0.0(您添加了对 png 文件的支持).如果你做了一个小改动，那么从 1.0.0.0 到 1.0.1.0(你修复了一些错误).
So If you make a major change move from version 1.0.0.0 to version 2.0.0.0 (you changed from WinForms to WPF for example). If you make a smaller change move from 1.0.0.0 to 1.1.0.0 (you added support for png files). If you make a minor change then go from 1.0.0.0 to 1.0.1.0 (you fixed some bugs).
如果您真的想获得详细信息，请使用最终编号作为内部版本编号，该编号会随着每次签入/提交而增加(但我认为这太过分了).
If you really want to get detailed use the final number as the build number which would increment for every checkin/commit (but I think that's going too far).
这篇关于最佳实践:软件版本控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！