GIT 或 SVN 或...面向前端开发人员 [英] GIT or SVN or... for front-end developers

问题描述

我最近开始在工作中将我们的一些项目导入 Subversion 存储库，在接下来的几周内，我希望团队中的每个人都负责他们自己的源代码控制管理.

I recently began importing a number of our projects into a Subversion repository at work and over the next few weeks i'm expecting every one on the team to take responsibility for their own source control management.

我选择 SVN 而不是 GIT 的原因是我希望团队中的每个人，包括设计师、前端人员、集成商......负责他们自己的 SCM，所以我期待事情会如果他们使用 GUI(Mac 的 Cornerstone 和 Windows 的 Tortoise SVN)管理他们的工作，他们会更快地移动.我知道那里有一些 GIT GUI，SmartGit 目前看起来最吸引人，但似乎没有一个能像他们的 SVN 同行那样强大.此外，我觉得如果不使用命令行来处理 DVCS，我们会在翻译中丢失一些东西(而我更喜欢使用 GUI 来管理 SVN 中的项目).

The reason I chose SVN over GIT is that I want everyone on the team, including designers, frontenders, integrators... to take charge of their own SCM and so i'm expecting things will move quicker if they manage their work using a GUI (Cornerstone for mac and Tortoise SVN for windows). I know there are some GIT GUIs out there, SmartGit looks most appealing at the minute, but none seem as capable as their SVN counterparts. Besides, I feel we'd be losing something in translation by not using the command line to work with a DVCS (whereas i'm significantly happier using a GUI to manage projects in SVN).

问题是分布式解决方案正在迅速超越集中式解决方案，因此我想知道现在是否真的值得额外投资，而不是必须在 6 个月后迁移所有内容并在 DVCS 上投入时间?另一种看待它的方式是，在此期间，SVN 将是一个相对轻松的步骤，如果我们以后决定迁移到 DVCS，这将使我们做好更充分的准备.

The problem is that distributed solutions are fast overtaking centralized solutions and so I'm wondering if it would really be worth the extra investment now rather than have to migrate everything 6 months down the line and invest time in a DVCS anyway? The other way to look at it is that SVN would be a relatively painless step in the meantime which would prepare us more adequately should we later decide to migrate to a DVCS.

感谢您的想法和经验.

*除此之外:出于多种原因，我更喜欢每个 SVN 存储库多个项目.然而，这意味着来自 Atlassian 的 Fisheye 的统计数据意义不大，而且更加混乱.如果我们确实决定使用 GIT，那么每个项目将有 1 个存储库.

*Aside: for a number of reasons, I prefer multiple projects per SVN repository. This, though, means less meaningful statistics from Atlassian's Fisheye, as well as being messier. If we did decide to use GIT it would be 1 repository per project.

推荐答案

关于 DVCS 要记住的一点是，它实际上并不是关于它的分布式，而是关于分支和合并.DVCS 使分支和合并变得更加容易，以至于每个开发人员/设计师/前端基本上都有自己的私有分支——他们的本地仓库.这样一来，他们就可以并行工作，而不会互相干扰.这意味着他们可以每隔几个小时检查一次代码，而不是等待几天，直到他们完成所有工作来检查代码.

One thing to keep in mind about DVCS is that it's not actually about the distributed-ness of it, it's about the branching and merging. DVCS makes branching and merging much easier, to the point that each developer/designer/front-ender basically has their own private branch -- their local repo. That way, they can work in parallel without stepping on each other's toes. That means they can be checking in code every few hours instead of waiting days until they have everything done to check it in.

我建议你看看 Mercurial.它在 TortoiseHg 中有一个很好的 GUI，我发现它比 Git 更容易上手，只是因为它并没有在一开始就为您提供所有高级的东西，但是一旦熟悉了系统，它仍然具有所有强大的功能.

I would suggest you look at Mercurial. It has a good GUI in TortoiseHg and I find it to be easier to get started with than Git, just because it doesn't present you with all the advanced stuff right at the beginning, but it still has all of the powerful functions once they're comfortable in the system.

这篇关于GIT 或 SVN 或...面向前端开发人员的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！