实现版本控制系统的好策略 [英] A good strategy for implementing a versioning system

问题描述

我一直在努力使用版本控制软件一段时间.我不是在谈论命名约定，而是在谈论如何在构建系统中实际应用一个版本，一直到发布.

I have been struggling with versioning software for a while now. I'm not talking about a naming convention, I'm talking about how to actually apply a version in a build system all the way through to a release.

我一般使用major.minor.maintenance-[发布类型]即 1.0.2-rc1

I generally use major.minor.maintenance-[release type] i.e. 1.0.2-rc1

问题在于管理版本号.我尝试了很多方法(将其粘贴在构建文件、属性文件、数据库等中)，但我还没有找到任何真正有效的方法.

The problem is managing the version number. I've tried many ways (sticking it in a build file, a properties file, a database, etc,etc) but I haven't found anything that really works well.

我想到的最接近的事情是使用我在此处记录的 Jira:http://blog.sysbliss.com/未分类/release-management-with-atlassian-bamboo-and-jira.html

The closest thing I came up with is using Jira which I documented here: http://blog.sysbliss.com/uncategorized/release-management-with-atlassian-bamboo-and-jira.html

我想知道是否有人对此有任何好的想法.另外，想知道人们如何处理发布版本......即如果我发布/部署版本 1.0.0-rc1 并在此版本中发现错误，然后登录到 1.0.0(下一个/生产版本).

I'm wondering if anyone has any good ideas about this. Also, wondering how people handle releasing a version.... i.e. If I release/deploy version 1.0.0-rc1 do bugs found in this release then get logged into 1.0.0 (the next/production release).

推荐答案

Microsoft 使用 ..-(或变体).

Microsoft uses <major>.<minor>.<patch>-<build number> (or a variation).

我喜欢使用 ..

这篇关于实现版本控制系统的好策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！