projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2e99b1e) | patch
Document how we do embargoed releases
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Fri, 26 Mar 2021 22:12:46 +0000 (22:12 +0000)
committerJunio C Hamano <gitster@pobox.com>
Sat, 27 Mar 2021 22:13:12 +0000 (15:13 -0700)
commit09420b7648eecf681c5393e3690301897397b30d
tree5e73e990f740d84cb5922de76e61ded3a1f085b4tree | snapshot
parent2e99b1e383d2da56c81d7ab7dd849e9dab5b7bf0commit | diff
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>
Documentation/Makefile diff | blob | blame | history
Documentation/howto/coordinate-embargoed-releases.txt [new file with mode: 0644] blob
Unnamed repository; edit this file 'description' to name the repository.