From 75741e4f1094dbeaeaae334028d8ed015cb3fb11 Mon Sep 17 00:00:00 2001 From: Jarek Potiuk Date: Sat, 4 Nov 2023 11:25:45 +0100 Subject: [PATCH] Change security.rst to use includes in providers The document was supposed to be generated dynamically at release time to add SBOM information but we can do it diffrently using Sphinx custom directives - similarly as we do with configuration. --- .../prepare_provider_packages.py | 24 ------------------ .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../apache-airflow-providers-ftp/security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 21 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../apache-airflow-providers-ssh/security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../security.rst | 22 +--------------- .../exts/includes/security.rst | 25 ------------------- 87 files changed, 85 insertions(+), 1833 deletions(-) rename dev/provider_packages/PROVIDER_SECURITY_TEMPLATE.rst.jinja2 => docs/exts/includes/security.rst (69%) diff --git a/dev/provider_packages/prepare_provider_packages.py b/dev/provider_packages/prepare_provider_packages.py index 546125acf9f84..dc95c54950164 100755 --- a/dev/provider_packages/prepare_provider_packages.py +++ b/dev/provider_packages/prepare_provider_packages.py @@ -1342,13 +1342,6 @@ def update_release_notes( regenerate_missing_docs, ): errors = True - if not update_security_rst( - jinja_context, - provider_package_id, - provider_details.documentation_provider_package_path, - regenerate_missing_docs, - ): - errors = True if not force: if not update_commits_rst( jinja_context, @@ -1551,23 +1544,6 @@ def update_changelog_rst( ) -def update_security_rst( - context: dict[str, Any], - provider_package_id: str, - target_path: Path, - regenerate_missing_docs: bool, -) -> bool: - return _update_file( - context=context, - template_name="PROVIDER_SECURITY", - extension=".rst", - file_name="security.rst", - provider_package_id=provider_package_id, - target_path=target_path, - regenerate_missing_docs=regenerate_missing_docs, - ) - - def update_commits_rst( context: dict[str, Any], provider_package_id: str, diff --git a/docs/apache-airflow-providers-airbyte/security.rst b/docs/apache-airflow-providers-airbyte/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-airbyte/security.rst +++ b/docs/apache-airflow-providers-airbyte/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-alibaba/security.rst b/docs/apache-airflow-providers-alibaba/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-alibaba/security.rst +++ b/docs/apache-airflow-providers-alibaba/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-amazon/security.rst b/docs/apache-airflow-providers-amazon/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-amazon/security.rst +++ b/docs/apache-airflow-providers-amazon/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-beam/security.rst b/docs/apache-airflow-providers-apache-beam/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-beam/security.rst +++ b/docs/apache-airflow-providers-apache-beam/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-cassandra/security.rst b/docs/apache-airflow-providers-apache-cassandra/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-cassandra/security.rst +++ b/docs/apache-airflow-providers-apache-cassandra/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-drill/security.rst b/docs/apache-airflow-providers-apache-drill/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-drill/security.rst +++ b/docs/apache-airflow-providers-apache-drill/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-druid/security.rst b/docs/apache-airflow-providers-apache-druid/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-druid/security.rst +++ b/docs/apache-airflow-providers-apache-druid/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-flink/security.rst b/docs/apache-airflow-providers-apache-flink/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-flink/security.rst +++ b/docs/apache-airflow-providers-apache-flink/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-hdfs/security.rst b/docs/apache-airflow-providers-apache-hdfs/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-hdfs/security.rst +++ b/docs/apache-airflow-providers-apache-hdfs/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-hive/security.rst b/docs/apache-airflow-providers-apache-hive/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-hive/security.rst +++ b/docs/apache-airflow-providers-apache-hive/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-impala/security.rst b/docs/apache-airflow-providers-apache-impala/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-impala/security.rst +++ b/docs/apache-airflow-providers-apache-impala/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-kafka/security.rst b/docs/apache-airflow-providers-apache-kafka/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-kafka/security.rst +++ b/docs/apache-airflow-providers-apache-kafka/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-kylin/security.rst b/docs/apache-airflow-providers-apache-kylin/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-kylin/security.rst +++ b/docs/apache-airflow-providers-apache-kylin/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-livy/security.rst b/docs/apache-airflow-providers-apache-livy/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-livy/security.rst +++ b/docs/apache-airflow-providers-apache-livy/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-pig/security.rst b/docs/apache-airflow-providers-apache-pig/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-pig/security.rst +++ b/docs/apache-airflow-providers-apache-pig/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-pinot/security.rst b/docs/apache-airflow-providers-apache-pinot/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-pinot/security.rst +++ b/docs/apache-airflow-providers-apache-pinot/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-spark/security.rst b/docs/apache-airflow-providers-apache-spark/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-spark/security.rst +++ b/docs/apache-airflow-providers-apache-spark/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apache-sqoop/security.rst b/docs/apache-airflow-providers-apache-sqoop/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apache-sqoop/security.rst +++ b/docs/apache-airflow-providers-apache-sqoop/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-apprise/security.rst b/docs/apache-airflow-providers-apprise/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-apprise/security.rst +++ b/docs/apache-airflow-providers-apprise/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-arangodb/security.rst b/docs/apache-airflow-providers-arangodb/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-arangodb/security.rst +++ b/docs/apache-airflow-providers-arangodb/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-asana/security.rst b/docs/apache-airflow-providers-asana/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-asana/security.rst +++ b/docs/apache-airflow-providers-asana/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-atlassian-jira/security.rst b/docs/apache-airflow-providers-atlassian-jira/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-atlassian-jira/security.rst +++ b/docs/apache-airflow-providers-atlassian-jira/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-celery/security.rst b/docs/apache-airflow-providers-celery/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-celery/security.rst +++ b/docs/apache-airflow-providers-celery/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-cloudant/security.rst b/docs/apache-airflow-providers-cloudant/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-cloudant/security.rst +++ b/docs/apache-airflow-providers-cloudant/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-cncf-kubernetes/security.rst b/docs/apache-airflow-providers-cncf-kubernetes/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-cncf-kubernetes/security.rst +++ b/docs/apache-airflow-providers-cncf-kubernetes/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-common-io/security.rst b/docs/apache-airflow-providers-common-io/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-common-io/security.rst +++ b/docs/apache-airflow-providers-common-io/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-common-sql/security.rst b/docs/apache-airflow-providers-common-sql/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-common-sql/security.rst +++ b/docs/apache-airflow-providers-common-sql/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-daskexecutor/security.rst b/docs/apache-airflow-providers-daskexecutor/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-daskexecutor/security.rst +++ b/docs/apache-airflow-providers-daskexecutor/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-databricks/security.rst b/docs/apache-airflow-providers-databricks/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-databricks/security.rst +++ b/docs/apache-airflow-providers-databricks/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-datadog/security.rst b/docs/apache-airflow-providers-datadog/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-datadog/security.rst +++ b/docs/apache-airflow-providers-datadog/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-dbt-cloud/security.rst b/docs/apache-airflow-providers-dbt-cloud/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-dbt-cloud/security.rst +++ b/docs/apache-airflow-providers-dbt-cloud/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-dingding/security.rst b/docs/apache-airflow-providers-dingding/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-dingding/security.rst +++ b/docs/apache-airflow-providers-dingding/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-discord/security.rst b/docs/apache-airflow-providers-discord/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-discord/security.rst +++ b/docs/apache-airflow-providers-discord/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-docker/security.rst b/docs/apache-airflow-providers-docker/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-docker/security.rst +++ b/docs/apache-airflow-providers-docker/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-elasticsearch/security.rst b/docs/apache-airflow-providers-elasticsearch/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-elasticsearch/security.rst +++ b/docs/apache-airflow-providers-elasticsearch/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-exasol/security.rst b/docs/apache-airflow-providers-exasol/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-exasol/security.rst +++ b/docs/apache-airflow-providers-exasol/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-facebook/security.rst b/docs/apache-airflow-providers-facebook/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-facebook/security.rst +++ b/docs/apache-airflow-providers-facebook/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-ftp/security.rst b/docs/apache-airflow-providers-ftp/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-ftp/security.rst +++ b/docs/apache-airflow-providers-ftp/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-github/security.rst b/docs/apache-airflow-providers-github/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-github/security.rst +++ b/docs/apache-airflow-providers-github/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-google/security.rst b/docs/apache-airflow-providers-google/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-google/security.rst +++ b/docs/apache-airflow-providers-google/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-grpc/security.rst b/docs/apache-airflow-providers-grpc/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-grpc/security.rst +++ b/docs/apache-airflow-providers-grpc/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-hashicorp/security.rst b/docs/apache-airflow-providers-hashicorp/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-hashicorp/security.rst +++ b/docs/apache-airflow-providers-hashicorp/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-http/security.rst b/docs/apache-airflow-providers-http/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-http/security.rst +++ b/docs/apache-airflow-providers-http/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-imap/security.rst b/docs/apache-airflow-providers-imap/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-imap/security.rst +++ b/docs/apache-airflow-providers-imap/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-influxdb/security.rst b/docs/apache-airflow-providers-influxdb/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-influxdb/security.rst +++ b/docs/apache-airflow-providers-influxdb/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-jdbc/security.rst b/docs/apache-airflow-providers-jdbc/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-jdbc/security.rst +++ b/docs/apache-airflow-providers-jdbc/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-jenkins/security.rst b/docs/apache-airflow-providers-jenkins/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-jenkins/security.rst +++ b/docs/apache-airflow-providers-jenkins/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-microsoft-azure/security.rst b/docs/apache-airflow-providers-microsoft-azure/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-microsoft-azure/security.rst +++ b/docs/apache-airflow-providers-microsoft-azure/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-microsoft-mssql/security.rst b/docs/apache-airflow-providers-microsoft-mssql/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-microsoft-mssql/security.rst +++ b/docs/apache-airflow-providers-microsoft-mssql/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-microsoft-psrp/security.rst b/docs/apache-airflow-providers-microsoft-psrp/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-microsoft-psrp/security.rst +++ b/docs/apache-airflow-providers-microsoft-psrp/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-microsoft-winrm/security.rst b/docs/apache-airflow-providers-microsoft-winrm/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-microsoft-winrm/security.rst +++ b/docs/apache-airflow-providers-microsoft-winrm/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-mongo/security.rst b/docs/apache-airflow-providers-mongo/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-mongo/security.rst +++ b/docs/apache-airflow-providers-mongo/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-mysql/security.rst b/docs/apache-airflow-providers-mysql/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-mysql/security.rst +++ b/docs/apache-airflow-providers-mysql/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-neo4j/security.rst b/docs/apache-airflow-providers-neo4j/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-neo4j/security.rst +++ b/docs/apache-airflow-providers-neo4j/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-odbc/security.rst b/docs/apache-airflow-providers-odbc/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-odbc/security.rst +++ b/docs/apache-airflow-providers-odbc/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-openfaas/security.rst b/docs/apache-airflow-providers-openfaas/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-openfaas/security.rst +++ b/docs/apache-airflow-providers-openfaas/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-openlineage/security.rst b/docs/apache-airflow-providers-openlineage/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-openlineage/security.rst +++ b/docs/apache-airflow-providers-openlineage/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-opensearch/security.rst b/docs/apache-airflow-providers-opensearch/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-opensearch/security.rst +++ b/docs/apache-airflow-providers-opensearch/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-opsgenie/security.rst b/docs/apache-airflow-providers-opsgenie/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-opsgenie/security.rst +++ b/docs/apache-airflow-providers-opsgenie/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-oracle/security.rst b/docs/apache-airflow-providers-oracle/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-oracle/security.rst +++ b/docs/apache-airflow-providers-oracle/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-pagerduty/security.rst b/docs/apache-airflow-providers-pagerduty/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-pagerduty/security.rst +++ b/docs/apache-airflow-providers-pagerduty/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-papermill/security.rst b/docs/apache-airflow-providers-papermill/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-papermill/security.rst +++ b/docs/apache-airflow-providers-papermill/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-plexus/security.rst b/docs/apache-airflow-providers-plexus/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-plexus/security.rst +++ b/docs/apache-airflow-providers-plexus/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-postgres/security.rst b/docs/apache-airflow-providers-postgres/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-postgres/security.rst +++ b/docs/apache-airflow-providers-postgres/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-presto/security.rst b/docs/apache-airflow-providers-presto/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-presto/security.rst +++ b/docs/apache-airflow-providers-presto/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-qubole/security.rst b/docs/apache-airflow-providers-qubole/security.rst index 66c6f79a4ecfc..b8f95e6ecfa29 100644 --- a/docs/apache-airflow-providers-qubole/security.rst +++ b/docs/apache-airflow-providers-qubole/security.rst @@ -16,23 +16,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-redis/security.rst b/docs/apache-airflow-providers-redis/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-redis/security.rst +++ b/docs/apache-airflow-providers-redis/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-salesforce/security.rst b/docs/apache-airflow-providers-salesforce/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-salesforce/security.rst +++ b/docs/apache-airflow-providers-salesforce/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-samba/security.rst b/docs/apache-airflow-providers-samba/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-samba/security.rst +++ b/docs/apache-airflow-providers-samba/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-segment/security.rst b/docs/apache-airflow-providers-segment/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-segment/security.rst +++ b/docs/apache-airflow-providers-segment/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-sendgrid/security.rst b/docs/apache-airflow-providers-sendgrid/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-sendgrid/security.rst +++ b/docs/apache-airflow-providers-sendgrid/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-sftp/security.rst b/docs/apache-airflow-providers-sftp/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-sftp/security.rst +++ b/docs/apache-airflow-providers-sftp/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-singularity/security.rst b/docs/apache-airflow-providers-singularity/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-singularity/security.rst +++ b/docs/apache-airflow-providers-singularity/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-slack/security.rst b/docs/apache-airflow-providers-slack/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-slack/security.rst +++ b/docs/apache-airflow-providers-slack/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-smtp/security.rst b/docs/apache-airflow-providers-smtp/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-smtp/security.rst +++ b/docs/apache-airflow-providers-smtp/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-snowflake/security.rst b/docs/apache-airflow-providers-snowflake/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-snowflake/security.rst +++ b/docs/apache-airflow-providers-snowflake/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-sqlite/security.rst b/docs/apache-airflow-providers-sqlite/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-sqlite/security.rst +++ b/docs/apache-airflow-providers-sqlite/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-ssh/security.rst b/docs/apache-airflow-providers-ssh/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-ssh/security.rst +++ b/docs/apache-airflow-providers-ssh/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-tableau/security.rst b/docs/apache-airflow-providers-tableau/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-tableau/security.rst +++ b/docs/apache-airflow-providers-tableau/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-tabular/security.rst b/docs/apache-airflow-providers-tabular/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-tabular/security.rst +++ b/docs/apache-airflow-providers-tabular/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-telegram/security.rst b/docs/apache-airflow-providers-telegram/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-telegram/security.rst +++ b/docs/apache-airflow-providers-telegram/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-trino/security.rst b/docs/apache-airflow-providers-trino/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-trino/security.rst +++ b/docs/apache-airflow-providers-trino/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-vertica/security.rst b/docs/apache-airflow-providers-vertica/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-vertica/security.rst +++ b/docs/apache-airflow-providers-vertica/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-yandex/security.rst b/docs/apache-airflow-providers-yandex/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-yandex/security.rst +++ b/docs/apache-airflow-providers-yandex/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/docs/apache-airflow-providers-zendesk/security.rst b/docs/apache-airflow-providers-zendesk/security.rst index 66c6f79a4ecfc..afa13dac6fc9b 100644 --- a/docs/apache-airflow-providers-zendesk/security.rst +++ b/docs/apache-airflow-providers-zendesk/security.rst @@ -1,4 +1,3 @@ - .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information @@ -16,23 +15,4 @@ specific language governing permissions and limitations under the License. -Releasing security patches --------------------------- - -Airflow providers are released independently from Airflow itself and the information about vulnerabilities -is published separately. You can upgrade providers independently from Airflow itself, following the -instructions found in :doc:`apache-airflow:installation/installing-from-pypi`. - -When we release Provider version, the development is always done from the ``main`` branch where we prepare -the next version. The provider uses strict `SemVer `_ versioning policy. Depending on -the scope of the change, Provider will get ''MAJOR'' version upgrade when there are -breaking changes, ``MINOR`` version upgrade when there are new features or ``PATCHLEVEL`` version upgrade -when there are only bug fixes (including security bugfixes) - and this is the only version that receives -security fixes by default, so you should upgrade to latest version of the provider if you want to receive -all released security fixes. - -The only exception to that rule is when we have a critical security fix and good reason to provide an -out-of-band release for the provider, in which case stakeholders in the provider might decide to cherry-pick -and prepare a branch for an older version of the provider following the -`mixed governance model `_ -and requires interested parties to cherry-pick and test the fixes. +.. include:: ../exts/includes/security.rst diff --git a/dev/provider_packages/PROVIDER_SECURITY_TEMPLATE.rst.jinja2 b/docs/exts/includes/security.rst similarity index 69% rename from dev/provider_packages/PROVIDER_SECURITY_TEMPLATE.rst.jinja2 rename to docs/exts/includes/security.rst index 56039a7761c0b..ee5a4768bd3ab 100644 --- a/dev/provider_packages/PROVIDER_SECURITY_TEMPLATE.rst.jinja2 +++ b/docs/exts/includes/security.rst @@ -1,28 +1,3 @@ -{# - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - "License"); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, - software distributed under the License is distributed on an - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY - KIND, either express or implied. See the License for the - specific language governing permissions and limitations - under the License. - - NOTE! THIS FILE IS AUTOMATICALLY GENERATED AND WILL BE - OVERWRITTEN WHEN PREPARING PACKAGES. - - IF YOU WANT TO MODIFY IT, YOU SHOULD MODIFY THE TEMPLATE - `PROVIDER_SECURITY_TEMPLATE.rst.jinja2` IN the `dev/provider_packages` DIRECTORY - -#} .. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information