diff options
| author |  Johannes Schindelin <johannes.schindelin@gmx.de> | 2021-03-26 22:12:46 +0000 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2021-03-27 15:13:12 -0700 |
| commit | 09420b7648eecf681c5393e3690301897397b30d (patch) | |
| tree | 5e73e990f740d84cb5922de76e61ded3a1f085b4 /levenshtein.c | |
| parent | SECURITY: describe how to report vulnerabilities (diff) | |
| download | tgif-09420b7648eecf681c5393e3690301897397b30d.tar.xz | |
Document how we do embargoed releases
Whenever we fix critical vulnerabilities, we follow some sort of
protocol (e.g. setting a coordinated release date, keeping the fix under
embargo until that time, coordinating with packagers and/or hosting
sites, etc).
Similar in spirit to `Documentation/howto/maintain-git.txt`, let's
formalize the details in a document.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'levenshtein.c')
0 files changed, 0 insertions, 0 deletions