@@ -219,7 +219,7 @@ The general labeling process should be consistent across artifact types.
219
219
referring to a release MAJOR.MINOR `vX.Y` version.
220
220
221
221
See also
222
- [release versioning](/contributors/design-proposals /release/versioning.md).
222
+ [release versioning](https://git.k8s.io/sig-release /release-engineering /versioning.md).
223
223
224
224
- *release branch*: Git branch `release-X.Y` created for the `vX.Y` milestone.
225
225
@@ -233,7 +233,7 @@ The general labeling process should be consistent across artifact types.
233
233
[ GitHub 里程碑] ( https://help.github.com/en/github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests )
234
234
指的是发布 主.次 ` vX.Y ` 版本。
235
235
236
- 另请参阅[ 发布版本控制] ( /contributors/design-proposals /release/versioning.md) 。
236
+ 另请参阅[ 发布版本控制] ( https://git.k8s.io/sig-release /release-engineering /versioning.md) 。
237
237
238
238
- ** 发布分支** :为 ` vX.Y ` 里程碑创建的 Git 分支 ` release-X.Y ` 。
239
239
@@ -504,14 +504,14 @@ Issues are marked as targeting a milestone via the Prow "/milestone" command.
504
504
The Release Team's [Bug Triage Lead](https://git.k8s.io/sig-release/release-team/role-handbooks/bug-triage/README.md)
505
505
and overall community watch incoming issues and triage them, as described in
506
506
the contributor guide section on
507
- [issue triage](/contributors/ guide/issue-triage.md ).
507
+ [issue triage](https://k8s.dev/docs/ guide/issue-triage/ ).
508
508
-->
509
509
### 问题补充 {#issue-additions}
510
510
511
511
通过 Prow “/milestone” 命令标记问题并指向里程碑。
512
512
513
513
发布团队的[ 错误分类负责人] ( https://git.k8s.io/sig-release/release-team/role-handbooks/bug-triage/README.md ) 和整个社区观察新出现的问题并对其进行分类,
514
- 在贡献者指南部分中描述[ 问题分类] ( /contributors/ guide/issue-triage.md ) 。
514
+ 在贡献者指南部分中描述[ 问题分类] ( https://k8s.dev/docs/ guide/issue-triage/ ) 。
515
515
516
516
<!--
517
517
Marking issues with the milestone provides the community better visibility
@@ -546,11 +546,11 @@ PR 通过 Prow “/milestone” 命令标记并指向里程碑。
546
546
<!--
547
547
## Other Required Labels
548
548
549
- [Here is the list of labels and their use and purpose.](https://git.k8s.io/test-infra/label*sync /labels.md#labels-that-apply-to-all-repos-for-both-issues-and-prs)
549
+ [Here is the list of labels and their use and purpose.](https://git.k8s.io/test-infra/label_sync /labels.md#labels-that-apply-to-all-repos-for-both-issues-and-prs)
550
550
-->
551
551
## 其他必需的标签 {#other-required-labels}
552
552
553
- [ 这里是标签列表及其用途和目的] ( https://git.k8s.io/test-infra/label*sync /labels.md#labels-that-apply-to-all-repos-for-both-issues-and-prs ) 。
553
+ [ 这里是标签列表及其用途和目的] ( https://git.k8s.io/test-infra/label_sync /labels.md#labels-that-apply-to-all-repos-for-both-issues-and-prs ) 。
554
554
555
555
<!--
556
556
### SIG Owner Label
@@ -650,11 +650,11 @@ Issue 类型用于帮助识别随着时间的推移进入版本的更改类型
650
650
- ` kind/feature ` :新功能
651
651
- ` kind/flake ` :CI 测试用例显示间歇性故障
652
652
653
- [ cherry-picks ] : /contributors/devel/sig-release/cherry-picks.md
653
+ [ cherry-picks ] : https://git.k8s.io/community /contributors/devel/sig-release/cherry-picks.md
654
654
[ code-freeze ] : https://git.k8s.io/sig-release/releases/release_phases.md#code-freeze
655
655
[ enhancements-freeze ] : https://git.k8s.io/sig-release/releases/release_phases.md#enhancements-freeze
656
656
[ exceptions ] : https://git.k8s.io/sig-release/releases/release_phases.md#exceptions
657
657
[ keps ] : https://git.k8s.io/enhancements/keps
658
- [ release-managers ] : https://kubernetes.io /releases/release-managers/
658
+ [ release-managers ] : /releases/release-managers/
659
659
[ release-team ] : https://git.k8s.io/sig-release/release-team
660
- [ sig-list ] : /sig-list.md
660
+ [ sig-list ] : https://k8s.dev/sigs
0 commit comments