如何设置理想的协作资源库设置？ [英] How to setup the ideal collaboration repository setup?

问题描述

我正在使用subversion和tourtiseSVN。

我正在寻找改变我的web开发团队的工作方式。我们致力于内部网站的内部开发。我们不会外包。我们希望增加从事特定产品开发的团队成员的数量。目前，我们的设置只允许1个成员在任何一个时间进行开发。这是因为我们在提交源代码库之前缺少一个分段区域，最终将其添加到生产中。

我已经在下面包含了一张图来演示我想要的内容实现。首先，一些说明：

环境X - 这是每个小组成员工作的地方。它是一个完整的版本库，其中的代码尚未提交到分期或生产。您会注意到我们有一些特殊的错误修复，它们会影响生产。这是必要的，因为不需要分期。

发展X - 这是特定区域的临时区域。我希望能够让一个以上的开发工作在同一个开发项目上（例如：一个新的图库模块）。我相信这个模型将允许2个成员在同一个开发和文件上工作，在一个临时区域进行提交和测试。然后，当所有由2名团队成员完成时，这些将被提交到生产存储库。

生产 - 这是用于生产产品的代码的存储库。

这是一个Web开发团队。我询问是否有人可以提供关于如何设置的提示，如果subversion是最好的，或者如果有更好的repostitory（必须允许在Linux上进行自我托管，并且有一种方法让windows机器与它交互，就像toirtoiseSVN一样）。所有的开发工作都在一个linux机器上完成，它可以通过Windows机器的网络访问。

ct4KT.jpgalt =建议模型的基本图解>

解决方案

使用分支。 发展A，生产和发展B是特别的分支。合作伙伴在同一分支上工作。准备好的开发分支合并到生产分支中。

只要支持分支机构，无论您决定使用哪个VCS，以上都应该可以使用。

我的建议离开SVN，因为使用SVN处理分支是一件很痛苦的事情。我喜欢去git。如果你切换到git，你会希望使用分支来处理所有事情，因为它们非常有用和无痛。

I'm currently using subversion and tourtiseSVN.

I am looking to revamp the way my web development team works. We work on inhouse developments for inhouse websites. We don't outsource. We would like to increase the number of team members working on an individual development on a particular product. At the moment, our setup only allows 1 member to work on a development at any one time. This is because we lack a 'staging' area before commiting to the source repository which eventually is added to production.

I have included a diagram below to demonstrate what I would like to achieve. First, some desciptions:

Dev Env X - This is where each invidual team member works. Its a complete copy of the repository which code which has yet to be commited to staging or production. You will notice we have some special ones which are for bug fixes which commit strait to production. This is nessary as there is no need for staging.

Development X - These are staging areas for a particular area. I would like to be able to allow more than 1 development to work on the same developemtn (ie: a new gallery module). I believe this model would allow 2 members to work on the same developement and files, the commit and test at a staging area. This will then be commited to the production repository when all is completed by the 2 team members

Production - this is the repository of the code that is used for the live produce.

This is for a web development team. I am asking if anyone can give tips on how to set this up, if subversion is the best or if there is a better repostitory out there (must allow self hosting on linux and have a way for windows machines to interface with it like toirtoiseSVN does). All development is done on a linux box which is accessed over a network by windows machines.

解决方案

Use branches. "Development A", "Production" and "Development B" are particular branches. People that collaborate work on the same branch. Development branches that are ready get merged into the production branch.

The above should work regardless of the VCS you decide to use as long as branches are supported.

My suggestion is to move away from SVN, because handling branches with SVN is such a pain. My preference goes to git. If you switch to git, you will want to use branches for everything, because they are so useful and painless.

这篇关于如何设置理想的协作资源库设置？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！