Create a script to consistently format patch files
cji opened this issue · comments
Based on feedback from distributors, we should automate creating consistent patch files when sending embargoed patches to distributors-announce@
- The patches should be a single commit (where possible)
- The patches should have any revision added to the file name (e.g. if we need to send out an updated patch, it should have a different filename than the original)
- The patches should be in a .zip file when sent via email
- The metadata at the top of the .patch file should look like:
From: distributors-announce <distributors-announce@kubernetes.io>
Date: Tue, 31 Oct 2023 18:23:55 +0000
Subject: Fix CVE-20XX-XXXX
---
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale