Drop Danger check related to pre-release testing

With the advent of the new development model involving security-*
branches and autorebasing, the value added by the pre-release testing
mechanism dropped drastically.  The only remaining benefit of
pre-release testing is flagging in-progress security fixes targeting
open source branches that conflict with the corresponding bind-9.x-sub
branches.  However, such conflicts are a rare occurrence and can be
handled after merging anyway.

Remove the Danger check related to pre-release testing.

diff --git a/dangerfile.py b/dangerfile.py
index 5cf06bce08614ea170a2f5ed1fb56b8f31e3547c..72ccab00aa62076fe43250e4914067e9f56ff241 100644 (file)
--- a/dangerfile.py
+++ b/dangerfile.py
@@ -524,25 +524,6 @@ if switches_added:
         "job to exercise the new build options added by this merge request."
     )
 
-###############################################################################
-# PRE-RELEASE TESTING
-###############################################################################
-#
-# WARN if the merge request is marked with the "Security" label, but not with
-# the label used for marking merge requests for pre-release testing (if the
-# latter is defined by the relevant environment variable).
-
-pre_release_testing_label = os.getenv("PRE_RELEASE_TESTING_LABEL")
-if (
-    pre_release_testing_label
-    and "Security" in mr_labels
-    and pre_release_testing_label not in mr_labels
-):
-    warn(
-        "This merge request is marked with the *Security* label, but it is not "
-        f"marked for pre-release testing (*{pre_release_testing_label}*)."
-    )
-
 ###############################################################################
 # USER-VISIBLE LOG LEVELS
 ###############################################################################