It's an open-source project, so could be described as following the Bazaar model. However I think this question is rooted in a misunderstanding of what that is.
There's nothing in that model to insist that any random rubbish gets committed to the code. I've never heard of an open-source project where that was the case (maybe because anything that did follow that would indeed be a tangled mess, and unlikely to be successful).
And again there's nothing in that model to say you can't have major version numbers. These are just a snapshot of the code at that point. You can download and deploy the code as it was one commit before or after version 1.0.2, with nothing to stop you.
发布评论
评论（1）
这是一个开源项目，因此可以描述为遵循 Bazaar 模型。 但我认为这个问题的根源在于对它是什么的误解。
该模型中没有任何内容可以坚持将任何随机垃圾提交到代码中。 我从来没有听说过有这样的开源项目（也许是因为接下来的任何事情确实会是一团混乱，而且不太可能成功）。
同样，该模型中没有任何内容表明您不能拥有主版本号。 这些只是当时代码的快照。 您可以下载并部署代码，因为它是版本 1.0.2 之前或之后的一次提交，没有什么可以阻止您。
It's an open-source project, so could be described as following the Bazaar model. However I think this question is rooted in a misunderstanding of what that is.
There's nothing in that model to insist that any random rubbish gets committed to the code. I've never heard of an open-source project where that was the case (maybe because anything that did follow that would indeed be a tangled mess, and unlikely to be successful).
And again there's nothing in that model to say you can't have major version numbers. These are just a snapshot of the code at that point. You can download and deploy the code as it was one commit before or after version 1.0.2, with nothing to stop you.