可配置软件的分支策略 [英] Branching strategy for configurable software

问题描述

我正在开发一个为各种客户生产的应用程序。根据客户的不同，软件的用户界面元素可能会有所不同。例如，一个客户可能需要菜单项X，而另一个客户获得菜单项Y.

I'm working on an application which is produced for various sets of customers. Depending on the customer, the software's user interface elements may vary. For example, one customer might need menu item X, while the another customer gets menu item Y.

目前，用户界面的所有配置都通过XML完成与春天）。对于不同的菜单选项示例，一个XML文件可能有一个菜单选项列表显示在UI上。

Currently all of the configuration for the user interface is done via XML (much of it with spring). For the different menu options example, one XML file might have a list of menu options to display on the UI.

我想知道如何最好地管理分支的软件，使他们都可以使用相同的核心基线，并且所有接收错误修复，更新等。分支之间唯一不同的是XML配置文件。

I'm trying to figure out how to best manage the branching of the software such that they can all use the same core baseline, and all receive bug fixes, updates, etc. The only thing that will be different between the branches is the XML configuration files.

有没有良好的实践/技巧来管理这个？我不完全确定每个客户需要不同的分支 - 这只是我的第一个想法，所以我打开其他建议。

Are there good practices/techniques for managing this? I'm not entirely sure that each customer needs different branches - that was just my first thought, so I'm open to other suggestions. But any help with how to best set this up would be appreciated.

如果它有助于知道，我们不使用分布式版本控制系统这个项目（使用SVN ）。

If it helps to know, we are not using a distributed version control system for this project (using SVN).

感谢，

Jeff

推荐答案

在trunk中，我会维护几个配置文件，以客户端命名。当准备交货时，我将仅复制相关的配置文件，按软件的预期重命名。

In the trunk, I would maintain several configuration files, named after the client. When preparing a delivery, I would copy only the relevant configuration file, renamed as expected by the software.

这篇关于可配置软件的分支策略的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！