本文介绍: GitLab源代码管理建立在 Git 之上,添加了旨在满足上述要求的功能。注意:SCM 不仅是 GitLab 中最常用的函数,也是历史最悠久的函数,因为它从一开始就存在。因此,我们收到了很多反馈,并积压了很长时间问题。因此,我们需要团队能力的相当一部分用于不是这一愿景核心问题,而是解决错误、稳定性、安全性和可扩展性,以保持我们的用户客户满意。随着跨职能安全合规性和增长团队的形成,或者新服务和库的创建,有效的协调和协作至关重要。直接分享您的反馈是为我们的战略和愿景做出贡献的最佳方式

Source Code Management

Introduction and how you can help

The Source Code Management direction page belongs to the Source Code group of the Create stage, and is maintained bDerek Ferguson, who can be reached at dferguson@gitlab.com.

This direction is a work in progress, and everyone can contribute. Sharing your feedback directly is the best way to contribute to our strategy and vision. Please, comment and contribute in the linked issues below, or to any other issues or epics, or raise an issue yourself in gitlab-org/gitlab if you don‘t find existing feedback that matches your thoughts.

源代码管理

简介以及如何提供帮助

源代码管理”方向页面属于创建阶段“源代码”组,由 Derek Ferguson 维护,可通过 dferguson@gitlab.com 联系到他。

这个方向一个正在进行的工作,每个人可以做出贡献。直接分享您的反馈是为我们的战略和愿景做出贡献的最佳方式。请在下面的链接问题或任何其他问题史诗中发表评论和贡献,或者如果您没有找到与您的想法相匹配的现有反馈,请在 gitlab-org/gitlab 中自行提出问题。

Strategy and Themes

Source code management (SCM) is the foundation of an organization‘s software development practice.

Building great software depends on teams working well together. Teams can rarely be divided into areas of complete independence. As crossfunctional security, compliance, and growth teams are formed, or new services and libraries are created, effective coordination and collaboration are essential.

To achieve this, teams need to protect production while making it easy for everyone to contribute. Source Code Management provides the controls to define the rules and workflows for this purpose:

战略和主题

代码管理 (SCM) 是组织软件开发实践的基础。

构建出色的软件取决于团队的良好合作团队很少可以划分为完全独立区域。随着跨职能安全合规性和增长团队的形成,或者新服务和库的创建,有效的协调和协作至关重要

为了实现这一目标,团队需要保护生产,同时让每个人都能轻松做出贡献。源代码管理提供了用于定义规则工作流的控件,以实现此目的:

Themes

While the principles have been around for half a century, SCM is not without challenges. SCM needs to address a large set of requirements that are partly contradicting:

主题

虽然这些原则已经存在了半个世纪,但 SCM 并非没有挑战。SCM 需要解决大量部分矛盾的需求

Git is the leading Version Control System (VCS) and is loved by developers. It excels at tracking changes in source code and makes it easy and transparent to merge changes from different developers into one code base. GitLab‘s source code management builds on top of Git adding functionality that aims to address the above requirements. For example, access control to code repositories or requiring code reviews before merging changes. Source code management and the create stage represent the most popular features in GitLab.

Git 是领先的版本控制系统 (VCS),深受开发人员的喜爱。它擅长跟踪源代码中的更改,并使将来自不同开发人员更改合并一个代码库中变得简单透明。GitLab 的源代码管理建立在 Git 之上,添加了旨在满足上述要求的功能例如,对代码存储库的访问控制或要求在合并更改之前进行代码审查。源代码管理和创建阶段代表了 GitLab 中最受欢迎的功能。

Yet, despite their appeal, neither Git nor GitLab SCM are perfect. Here are the current main shortcomings:

然而,尽管它们很有吸引力,但 Git 和 GitLab SCM 都不是完美的。以下是目前的主要缺点:

Strategy

Therefore, the vision for Source Code Management at GitLab consists of three pillars:

策略

因此,GitLab 的源代码管理愿景由三大支柱组成:

Note: SCM is not only the most used function in GitLab but also the one with the longest history as it has been there from the beginning. As a result, we get a lot of feedback and have a long backlog of issues. Therefore, we need to spend a considerable share of our teams’ capacity on issues that are not at the center of this vision but address bugs, stability, security, and scalability to keep our users and customers happy.

注意:SCM 不仅是 GitLab 中最常用的函数,也是历史最悠久的函数,因为它从一开始就存在。因此,我们收到了很多反馈,并积压了很长时间的问题。因此,我们需要将团队能力的相当一部分用于不是这一愿景核心的问题,而是解决错误、稳定性、安全性和可扩展性,以保持我们的用户客户满意。

摘自:

分类方向 – 源代码管理 | GitLab的

原文地址:https://blog.csdn.net/asdcls/article/details/134728696

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任

如若转载,请注明出处:http://www.7code.cn/show_24212.html

如若内容造成侵权/违法违规/事实不符,请联系代码007邮箱suwngjj01@126.com进行投诉反馈,一经查实,立即删除

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注