我需要你关于 svn 和 bug 跟踪系统的建议

发布于 2024-10-10 10:35:24 字数 354 浏览 0 评论 0原文

我们是埃及的一家初创公司,员工人数约为20名员工,我们真正需要的是:

  1. 错误跟踪系统
  2. 我们有一台服务器,我们想在本地服务器中管理我们的源代码,所以我们想要颠覆服务器安装并允许所有用户访问本地服务器并提交、更新和进行版本管理
  3. 每个员工都会有一个 svn 客户端
  4. 我们还需要任务管理来让经理划分任务并将其分配给我

在互联网上提供服务的员工,我发现有很多选项,例如(Trac、VisualSVN、CVS 等),但我不太明白 SVN、CVS 之间的区别,以及是否有其他一些我们可以使用的选项开源应用程序,以及如何使它们一起工作

请任何人尽快帮忙回复 提前

致谢

we are a starting company in Egypt, the number of employees is about 20 employee , what we are really need is :

  1. bug tracing system
  2. we have a server and we want to manage our source code in our local server , so we want subversion server to install and allow all users to access the local server and commit, update and make version management
  3. every employee will have a svn client
  4. we want also task management to let managers to divide tasks and assign them to employees

I have served the internet and i have found a lot of options like (Trac , VisualSVN ,CVS , etc) but i don't really understand the difference between SVN , CVS and if there are some other options open source application that we can use , and how to make them all work together

please is any one can help reply as soon as he/she can

Thanks in Advance

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

梦中的蝴蝶 2024-10-17 10:35:24

CVS 已经过时了。您真正的需求应该是,如果您想使用 Subversion、占主导地位的集中式 VCS 或许多流行的 DVCS(如 Git 或 Mercurial)。

通常,公司更喜欢集中式版本控制,您可以提交集中式 Subversion 存储库,或者像使用 Git 或 Mercurial 那样使用点对点模型。然而,开源社区、github、codeplex、code.google.com 和 bitbucket 的流行让 DVCS 变得兴奋起来。

几乎所有版本控制都带有 IDE 集成 - VisualHG、VisualSVN 等。当然,subversion 可视化工具更加成熟并且已经存在了一段时间。

Trac 是一个增强的 wiki 和问题跟踪系统,并且具有与 Subversion 和 Mercurial 的集成支持,因此这不应该成为问题。

SO 中有很多关于这个主题的讨论和网络上的文献。

您可以研究颠覆的弱点,特别是弱合并/困难的分支能力,以及其中一些 DVCS 如何克服它们。

CVS is outdated. Your real requirement should be, if you want to use Subversion, the dominant centralized VCS or many of the DVCS in vogue like Git or Mercurial.

Typically companies prefer centralized version control where you commit to centralized subversion repository or work on peer to peer model as with Git or Mercurial. How ever, open source community, popularity of github, codeplex, code.google.com and bitbucket places the excitement in hands of DVCSs.

Almost all version controls comes with IDE integration - VisualHG, VisualSVN, .. etc. Of course, the subversion visual tools are more mature and has been around for some time.

Trac is an enhanced wiki and issue tracking system and has integration support with both Subversion and Mercurial, so that should not be an issue.

There are quite some discussion in SO on this subject and literature on the web.

You can look into weaknesses of subversion, specially weak merging / difficult branching abilities and also how some of these DVCSes overcome them.

巡山小妖精 2024-10-17 10:35:24

我会认真考虑 Mercurial。它是分布式源控制系统,提供与任何系统相同的功能,但支持完全无连接的环境。意思就是这个。传统上,只有一个公共服务器,即源服务器。客户端连接到服务器,创建快照,修改文件,然后再次将它们检回服务器。这意味着您必须在线并且服务器也必须在线。

对于 Mercurial,情况有所不同。是的,仍然有一个主副本。然而,在去那里之前,代码实际上是在本地签入的。这意味着在代码最终到处都是之前,您可以完全自由地进行多少更改。分支非常简单且有效...好吧,我只是建议您在做出选择并选择 SVN 或 CVS 或 Perforce 或(上帝禁止)TFS 之前,也仔细考虑一下 Mercurial。

至于错误跟踪,Jira 是大多数小公司广泛使用的系统。非常有效、高度可定制、适合 SCRUM、支持工作流程、大量插件以及与 Fisheye 轻松集成等。

I would seriously consider Mercurial. It's distributed source control system providing the same functionality as any of the systems but bolsters completely connectionless environment. What it means is this. Classically there is one common server, the source. Client connect to is, create snapshots, modify files and check them back into the server again. This means you have to be online and the server has to be online.

With Mercurial it's different. Yes, there still is a master copy. However before going to there, the code is actually checked in locally. This means there is absolute freedom in how many changes you made before the code end up everywhere. Branching is very simple and effective as well... Well, I just suggest before you make your choice and pick SVN or CVS or Perforce or, God forbid, TFS, carefully consider Mercurial as well.

As for bug tracking, Jira is a system widely used by most of small companies. Very effective, highly customizable, fit for SCRUM, supports workflow, lots of plugins and easy integration with Fisheye, etc.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文