提交 fbb76bd0 编写于 作者: T Tomas Vik

Merge branch 'update-development-process' into 'main'

docs: update development process with new team info

See merge request gitlab-org/gitlab-vscode-extension!127
......@@ -8,12 +8,12 @@ This document describes how we make changes to the extension. For contributing g
## Who reviews the changes?
**Any member of the Create:Editor team** (either [FE] or [BE]) can review a change (MR). Each MR should have at least one review. At the moment, we don't want to have any more complexity in the process. The review is mainly for knowledge sharing and sanity checking. It's not a full sign off the same way maintainer would sing off change to GitLab project.
**Any member of the Create:Code Review team** (either [FE] or [BE]) can review a change (MR). Each MR should have at least one review. At the moment, we don't want to have any more complexity in the process. The review is mainly for knowledge sharing and sanity checking. It's not a full sign off the same way maintainer would sing off change to GitLab project.
## Who releases the changes?
Only [project maintainers] can tag a release. Follow the [release process](release-process.md).
[FE]: https://about.gitlab.com/handbook/engineering/development/dev/create-editor-fe/
[BE]: https://about.gitlab.com/handbook/engineering/development/dev/create-editor-be/
[FE]: https://about.gitlab.com/handbook/engineering/development/dev/create-code-review-fe/
[BE]: https://about.gitlab.com/handbook/engineering/development/dev/create-code-review-be/
[project maintainers]: https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/project_members?sort=access_level_desc
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册