On a Monday in 2022, Peter Krempa wrote:
The 'Branch fixing policy' paragraph claims that we have at least one actively maintained stable branch which isn't currently the case. Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx> --- docs/securityprocess.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/securityprocess.rst b/docs/securityprocess.rst index adddbf76b0..e1dc626f68 100644 --- a/docs/securityprocess.rst +++ b/docs/securityprocess.rst @@ -84,8 +84,8 @@ engineers on the security team. Branch fixing policy -------------------- -The libvirt community maintains one or more stable release branches at any given -point in time. The security team will aim to publish fixes for GIT master (which -will become the next major release) and each currently maintained stable release -branch. The distro maintainers will be responsible for backporting the -officially published fixes to other release branches where applicable. +The security team will aim to publish fixes for GIT master (which will become +the next major release) and each currently maintained stable release branch, if +there's any.
Maybe you can drop the mention of stable releases completely. The last one was in 2017 if https://wiki.libvirt.org/page/Maintenance_Releases is to be trusted. Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx> Jano
+The distro maintainers will be responsible for backporting the officially +published fixes to other release branches where applicable. -- 2.35.1
Attachment:
signature.asc
Description: PGP signature
