Skip to content

fix-readme-1-31 #2910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sakshi-shukla01 wants to merge 1 commit into
base: master
Choose a base branch
from
+214,689 −214,690
Open

fix-readme-1-31 #2910

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
The diff you're trying to view is too large. We only load the first 3000 changed files.
52 changes: 26 additions & 26 deletions .github/ISSUE_TEMPLATE/bug-report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,26 +1,26 @@
---
name: Bug Report
about: Report a SIG Release bug
labels: kind/bug, sig/release

---

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->

#### What happened:

#### What you expected to happen:

#### How to reproduce it (as minimally and precisely as possible):

#### Anything else we need to know?:

#### Environment:

- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Others:
---
name: Bug Report
about: Report a SIG Release bug
labels: kind/bug, sig/release
---
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
#### What happened:
#### What you expected to happen:
#### How to reproduce it (as minimally and precisely as possible):
#### Anything else we need to know?:
#### Environment:
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Others:
306 changes: 153 additions & 153 deletions .github/ISSUE_TEMPLATE/cut-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,153 +1,153 @@
---
name: Cut a release
about: Create a tracking issue for a release cut
title: Cut v1.x.y-{alpha,beta,rc}.z release
labels: sig/release, area/release-eng
---
## Scheduled to happen: <!-- Tue, YYYY-MM-DD -->

_Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of [`krel fast-forward`](https://testgrid.k8s.io/sig-release-releng-blocking#git-repo-kubernetes-fast-forward)
to avoid conflicts with releases running in parallel. The fast-forward will
automatically stop once the v1.x.0 tag is available._

## Release Blocking Issues
<!--

Make a list of anything preventing the release to start
(failing tests, pending image bumps, etc) and link them
to the relevant GitHub issues:

- [ ] Issue 1
- [ ] Issue 2

-->

<!--

Release Process Steps:
======================

Create a thread on #release-management on Slack to notify updates
about the release. For example,
- https://kubernetes.slack.com/archives/CJH2GBF7Y/p1635868822040300
- https://kubernetes.slack.com/archives/CJH2GBF7Y/p1631606375087500

- Add/Remove items of the checklist as you see fit
- Post bumps or issues encountered along the way

Hints and pointers to docs for each step of the release process:

Screenshot Testgrid Boards:
Use `krel testgridshot` to automatically create the screenshots
http://bit.ly/relmanagers-handbook#testgrid-screenshots

Stage and Release (mock and nomock):
Use `krel stage` && `krel release` see the handbook for more:
http://bit.ly/relmanagers-handbook#releases-management

Image promotion:
Use `kpromo pr` to create a pull request
https://sigs.k8s.io/promo-tools/docs/promotion-pull-requests.md

Notify #release-management on Slack:
Announce the release in a message in the Channel and paste the link
Direct link to slack: https://kubernetes.slack.com/messages/CJH2GBF7Y

Send notification:
Use `krel announce` using your Sendgrid token
http://bit.ly/relmanagers-handbook#sending-mail

Collect Metrics:
Run krel history --branch release-1.mm --date-from 2021-mm-dd
http://bit.ly/relmanagers-handbook#adding-data-about-the-cloud-build-jobs

Finish post-release branch creation tasks: ← Only for rc.0 release
See the Branch Creation section of the handbook for more details:
http://bit.ly/relmanagers-handbook#branch-creation

Help? Ring @release-managers on slack!

-->

## Release Steps

- [ ] Ensure a green signal has been given by Release Signal **on the day of the cut**
- [ ] Create a thread on #release-management: <!-- Paste link to slack -->
- [ ] Screenshot unhealthy release branch testgrid boards
- [ ] Check the health of the publishing-bot <!-- check if https://github.com/kubernetes/kubernetes/issues/56876 is closed -->
- Mock Run
- [ ] Stage
- [ ] Release
- NoMock Run
- [ ] Stage
- [ ] Image Promotion PR: <!-- Paste Pull Request URL here -->
- [ ] Release
- [ ] Send email notification: <!-- Paste link to kubernetes-dev email -->
- [ ] Notify #release-management on Slack: <!-- Paste link to slack -->
- [ ] Update [`schedule.yaml` file](https://github.com/kubernetes/website/blob/main/data/releases/schedule.yaml) with the latest release using [`schedule-builder`](https://github.com/kubernetes/release/tree/master/cmd/schedule-builder) (_patch releases only_) <!-- Paste Pull Request URL here -->
- [ ] Collect metrics and add them to the `Release steps` table below through `krel history --branch release-1.xx --date-from yyyy-mm-dd` (current date)
<!-- ONLY FOR RC.0 RELEASES - [ ] Post-release branch creation tasks -->
<!-- ONLY FOR .0 RELEASE - [ ] Code Thaw PR merged and OBS project created for the new minor release -->

## Release Tools Version

<!-- Replace with output of `krel version` -->
```
GitVersion: vM.m.p
GitCommit: 191ddd0b0b49af1adb04a98e45cebdd36cae9307
GitTreeState: clean
BuildDate: YYYY-MM-DDTHH:mm:ssZ
GoVersion: go1.16.3
Compiler: gc
Platform: linux/amd64
```

## Release Jobs History

<!-- The following table can be automatically generated using krel --history -->
| Step | Command | Link | Start | Duration | Succeeded? |
| --- | --- | --- | --- | --- | --- |
| Mock stage | `krel stage [arguments]` | | | | |
| Mock release | `krel release [arguments]` | | | | |
| Stage | `krel stage [arguments]` | | | | |
| Release | `krel release [arguments]` | | | | |

## Action Items

<!--
During the release, you may find a few things that require updates
(process changes, documentation updates, fixes to release tooling).

Please list them here.

It will be your responsibility to open issues/PRs to resolve these
issues/improvements. Keep this issue open until these action items
are complete.

- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->

## Open Questions

<!--
During the release, you may have a few questions that you can't
answer yourself or may require group discussion.

Please list them here.

Follow up with Branch Managers/Patch Release Team/Release Engineering
subproject owners to get these questions answered.

- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->

/milestone <!-- v1.x e.g. v1.14 -->
/assign <!-- @ the Release Manager responsible for this release -->
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
---
name: Cut a release
about: Create a tracking issue for a release cut
title: Cut v1.x.y-{alpha,beta,rc}.z release
labels: sig/release, area/release-eng
---
## Scheduled to happen: <!-- Tue, YYYY-MM-DD -->
_Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of [`krel fast-forward`](https://testgrid.k8s.io/sig-release-releng-blocking#git-repo-kubernetes-fast-forward)
to avoid conflicts with releases running in parallel. The fast-forward will
automatically stop once the v1.x.0 tag is available._
## Release Blocking Issues
<!--
Make a list of anything preventing the release to start
(failing tests, pending image bumps, etc) and link them
to the relevant GitHub issues:
- [ ] Issue 1
- [ ] Issue 2
-->
<!--
Release Process Steps:
======================
Create a thread on #release-management on Slack to notify updates
about the release. For example,
- https://kubernetes.slack.com/archives/CJH2GBF7Y/p1635868822040300
- https://kubernetes.slack.com/archives/CJH2GBF7Y/p1631606375087500
- Add/Remove items of the checklist as you see fit
- Post bumps or issues encountered along the way
Hints and pointers to docs for each step of the release process:
Screenshot Testgrid Boards:
Use `krel testgridshot` to automatically create the screenshots
http://bit.ly/relmanagers-handbook#testgrid-screenshots
Stage and Release (mock and nomock):
Use `krel stage` && `krel release` see the handbook for more:
http://bit.ly/relmanagers-handbook#releases-management
Image promotion:
Use `kpromo pr` to create a pull request
https://sigs.k8s.io/promo-tools/docs/promotion-pull-requests.md
Notify #release-management on Slack:
Announce the release in a message in the Channel and paste the link
Direct link to slack: https://kubernetes.slack.com/messages/CJH2GBF7Y
Send notification:
Use `krel announce` using your Sendgrid token
http://bit.ly/relmanagers-handbook#sending-mail
Collect Metrics:
Run krel history --branch release-1.mm --date-from 2021-mm-dd
http://bit.ly/relmanagers-handbook#adding-data-about-the-cloud-build-jobs
Finish post-release branch creation tasks: ← Only for rc.0 release
See the Branch Creation section of the handbook for more details:
http://bit.ly/relmanagers-handbook#branch-creation
Help? Ring @release-managers on slack!
-->
## Release Steps
- [ ] Ensure a green signal has been given by Release Signal **on the day of the cut**
- [ ] Create a thread on #release-management: <!-- Paste link to slack -->
- [ ] Screenshot unhealthy release branch testgrid boards
- [ ] Check the health of the publishing-bot <!-- check if https://github.com/kubernetes/kubernetes/issues/56876 is closed -->
- Mock Run
- [ ] Stage
- [ ] Release
- NoMock Run
- [ ] Stage
- [ ] Image Promotion PR: <!-- Paste Pull Request URL here -->
- [ ] Release
- [ ] Send email notification: <!-- Paste link to kubernetes-dev email -->
- [ ] Notify #release-management on Slack: <!-- Paste link to slack -->
- [ ] Update [`schedule.yaml` file](https://github.com/kubernetes/website/blob/main/data/releases/schedule.yaml) with the latest release using [`schedule-builder`](https://github.com/kubernetes/release/tree/master/cmd/schedule-builder) (_patch releases only_) <!-- Paste Pull Request URL here -->
- [ ] Collect metrics and add them to the `Release steps` table below through `krel history --branch release-1.xx --date-from yyyy-mm-dd` (current date)
<!-- ONLY FOR RC.0 RELEASES - [ ] Post-release branch creation tasks -->
<!-- ONLY FOR .0 RELEASE - [ ] Code Thaw PR merged and OBS project created for the new minor release -->
## Release Tools Version
<!-- Replace with output of `krel version` -->
```
GitVersion: vM.m.p
GitCommit: 191ddd0b0b49af1adb04a98e45cebdd36cae9307
GitTreeState: clean
BuildDate: YYYY-MM-DDTHH:mm:ssZ
GoVersion: go1.16.3
Compiler: gc
Platform: linux/amd64
```
## Release Jobs History
<!-- The following table can be automatically generated using krel --history -->
| Step | Command | Link | Start | Duration | Succeeded? |
| --- | --- | --- | --- | --- | --- |
| Mock stage | `krel stage [arguments]` | | | | |
| Mock release | `krel release [arguments]` | | | | |
| Stage | `krel stage [arguments]` | | | | |
| Release | `krel release [arguments]` | | | | |
## Action Items
<!--
During the release, you may find a few things that require updates
(process changes, documentation updates, fixes to release tooling).
Please list them here.
It will be your responsibility to open issues/PRs to resolve these
issues/improvements. Keep this issue open until these action items
are complete.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
## Open Questions
<!--
During the release, you may have a few questions that you can't
answer yourself or may require group discussion.
Please list them here.
Follow up with Branch Managers/Patch Release Team/Release Engineering
subproject owners to get these questions answered.
- [ ] Item 1
- [ ] Item 2
- [ ] Item 3
-->
/milestone <!-- v1.x e.g. v1.14 -->
/assign <!-- @ the Release Manager responsible for this release -->
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
22 changes: 11 additions & 11 deletions .github/ISSUE_TEMPLATE/feature.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
name: Feature Request
about: Suggest a SIG Release feature
labels: kind/feature, sig/release

---
<!-- Please only use this template for submitting feature requests -->

#### What would you like to be added:

#### Why is this needed:
---
name: Feature Request
about: Suggest a SIG Release feature
labels: kind/feature, sig/release
---
<!-- Please only use this template for submitting feature requests -->
#### What would you like to be added:
#### Why is this needed:
Loading
Loading