Skip to content
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

Remove rapture reference #2354

Merged
merged 1 commit into from
Oct 10, 2023
Merged

Remove rapture reference #2354

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
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions release-engineering/packaging.md
View file
Open in desktop

This file was deleted.

7 changes: 0 additions & 7 deletions release-engineering/role-handbooks/branch-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,6 @@
- [Official Releases](#official-releases)
- [Security fixes](#security-fixes)
- [Announcing Security Fixes](#announcing-security-fixes)
- [Debian and RPM Packaging](#debian-and-rpm-packaging)
- [Release Validation](#release-validation)
- [Post-release Activities](#post-release-activities)
- [Update kubekins-e2e variants](#update-kubekins-e2e-variants)
Expand Down Expand Up @@ -493,12 +492,6 @@ krel cve edit CVE-2022-0000 -f ./path-to-data-map.yaml

This command will also take care of validating the provided data map file. Once the data maps are uploaded, `krel` will (automatically) take those data maps into account when generating the changelog and the release announcement emails.

#### Debian and RPM Packaging

Publishing the [packages of the official release](https://github.com/kubernetes/sig-release/blob/master/release-engineering/packaging.md) is by conducted by employees at Google. Once `krel release --nomock --type=official …` has completed (which builds the packages into the production bucket), **before sending out the email notification**, contact the [Release Managers Google Group][release-managers-group] to notify them that an official release for `vX.Y` is complete and the packages are ready to be published.

Once the .deb and .rpm packages are published, you can `grep` for `X.Y` e.g. `1.16` in the [yum](https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/primary.xml) and [apt](https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/Packages) repositories.

#### Release Validation

The following are some ways to determine if the release process was successful:
Expand Down