openstack/releases
Code Issues Proposed changes

Send RC announces to release-announce

Browse Source 
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
This commit is contained in:
Thierry Carrez 2019-10-08 13:47:13 +02:00
parent 308bfe7cdf
commit f32b877ece
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
openstack_releases/release_notes.py
View File

@ -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({