在多个开发人员之间使用Trunk / Branches和Tag结构(Using Trunk / Branches and Tag structure between multiple developers)

 当涉及到Trunk / Branches和Tags时，我最终会感到困惑。 以下是我的查询： 
 
 我们有一个开发团队在一个项目上工作。 开发人员通常分组，他们在同一个项目上处理各种模块。 
 
 目前，我们有一个简单的SVN系统（没有任何Trunk / Branches或Tags），每个人都在同一个本地服务器上工作并提交文件。 但问题出现的时候，有几个开发人员在研究未来的模块（不应该立即上线）。 在这种情况下，他们无法提交数据，因为如果他们这样做，他们的开发代码将上传到实时服务器上，最终会弄乱一切。 
 
 所以，现在我正在寻找某种解决方案，这些开发人员可以单独工作但是使用相同的代码。 像这样的东西： 
 
 开发人员A正在开发新模块A开发人员B正在开发新模块B开发人员C正在开发模块C的漏洞修复（已经在线，但很少有错误需要修复） 
 
 因此，开发人员A将在此计算机上拥有自己的副本，并将提交到Developer A的存储库。 （或分支） 
 
 同样的逻辑适用于开发人员B，但开发人员C将处理一个常见的稳定副本，该副本将位于标签中，一旦工作完成，它将被标记并推送到主干服务器上传的主干。 
 
 一旦开发人员A完成了工作，他就会将所有文件推送到Trunk进行实时上传。 （这也应该合并trunk中的一些常见文件）。 同样的逻辑适用于Developer B. 
 
 我不确定SVN是否适合这个解决方案。 我甚至不知道是否有更简单的方法来实现我想要的东西。 
 
 欢迎提出任何建议。 
 
 谢谢TTR 

I end up getting confused when it comes to Trunk / Branches and Tags. Following is my query:
 
We have a team of developers working on a single project. The developers are often divided in groups and they work on various modules on the same project.
 
Currently, we have a simple SVN system (without any Trunk / Branches or Tags) where everyone works on the same local server and commits the files. But the problem starts when, a couple of developers work on future modules (which are not supposed to go live immediately). In this situation, they cannot commit the data because if they do, their development code will be uploaded on the live server and it will end up messing up everything. 
 
So, now I am looking for some kind of solution where, these developers can work separately but on the same code. Something like this:
 
Developer A is working on New Module A Developer B is working on New Module B Developer C is working on Bug Fixes of Module C (which is already on live but few bugs needs to be fixed)
 
So, Developer A will have it's own copy on this machine and will commit to Developer A's repository. (Or Branch)
 
The same logic applies to Developer B but Developer C will be working on a common stable copy which will be somewhere in Tags and once the work is done, it will be tagged and pushed to the Trunk for the upload on live server.
 
Once Developer A is done with the work, he will push all his files to Trunk for live upload. (This should merge some common files in trunk too). Same logic applies to Developer B.
 
I am not sure if SVN will be the right solution for this or not. I don't even know if there is any simpler way to implement what I want.
 
Any kind of suggestions are welcome.
 
Thanks TTR

原文：https://stackoverflow.com/questions/4584379