From f32b877ece52ecb0518cefadb328bf276376a2a7 Mon Sep 17 00:00:00 2001 From: Thierry Carrez Date: Tue, 8 Oct 2019 13:47:13 +0200 Subject: [PATCH] Send RC announces to release-announce All releases are announced to the release-announce ML, except Release candidates, which were still sent to openstack-discuss. The rationale was that RCs should be announced to a developers list rather than a downstream consumers list, so that they trigger testing. But that is less true now that there is a single -discuss list, where they generate a lot of noise around RC1, without triggering any additional testing. They also confuse some downstream consumers which expect those to go to the usual release announce list. This patch removes the exception and makes sure we send all RC announces to the release-announce list. Change-Id: Id33dba37b4d53962a2170ec401499fe3dd2e24bf --- openstack_releases/release_notes.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/openstack_releases/release_notes.py b/openstack_releases/release_notes.py index 0e5a7c9a57..3094a58229 100644 --- a/openstack_releases/release_notes.py +++ b/openstack_releases/release_notes.py @@ -374,12 +374,10 @@ def generate_release_notes(repo, repo_path, # The recipient for announcements should always be the # release-announce@lists.openstack.org ML (except for - # release-test and release candidates) + # release-test) email_to = 'release-announce@lists.openstack.org' if repo_name == 'openstack-release-test': email_to = 'release-job-failures@lists.openstack.org' - elif is_release_candidate: - email_to = 'openstack-discuss@lists.openstack.org' params = dict(sections) params.update({