From 52d0666934966dd50608ad456104ec21460b29b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Natal=20Ng=C3=A9tal?= Date: Tue, 22 Jan 2019 16:43:43 +0100 Subject: [PATCH] [Documentation] Change openstack-dev to openstack-discuss. The openstack-dev address is replaces by openstack-discuss. Change-Id: I4b33648ff9b4244b9d61548ca0e395f222ce0488 --- doc/source/open-source.rst | 6 +++--- doc/source/release-management.rst | 4 ++-- doc/source/stable-branches.rst | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/open-source.rst b/doc/source/open-source.rst index af78949..b42df1b 100644 --- a/doc/source/open-source.rst +++ b/doc/source/open-source.rst @@ -50,9 +50,9 @@ licensed, contributors need to understand how the interaction between the modules will work and the compatibility of the licenses involved. Please read the `licensing requirements`_, and if there are any remaining doubts or concerns, it is recommended to contact the Technical Committee (using the -openstack-dev mailing-list with the [tc] prefix, or on the #openstack-tc IRC -channel) to discuss with the Technical Committee how to proceed. In general, -err on the side of caution here. +openstack-discuss mailing-list with the [tc] prefix, or on the #openstack-tc +IRC channel) to discuss with the Technical Committee how to proceed. In +general, err on the side of caution here. With regards to dependencies, any third-party libraries or modules need to be vetted in the `global requirements`_. This ensures the added requirement of diff --git a/doc/source/release-management.rst b/doc/source/release-management.rst index 2a61a93..12680a4 100644 --- a/doc/source/release-management.rst +++ b/doc/source/release-management.rst @@ -264,7 +264,7 @@ must ensure they are done by someone on the project team. topics. The primary means of communication between the release management - team and other project teams is the openstack-dev mailing + team and other project teams is the openstack-discuss mailing list. Liaisons must be subscribed and ensure that they pay attention to threads with the topic "[release]". Watch for instructions related to deadlines, release changes that need to be @@ -339,7 +339,7 @@ time to stabilize and for the owners to prepare bug fixes if needed. causing regressions is low. To request an exception for a library release past the freeze, send - an email to the openstack-dev mailing list with the following tags + an email to the openstack-discuss mailing list with the following tags in the subject line:: [release][requirements][other-impacted-projects] diff --git a/doc/source/stable-branches.rst b/doc/source/stable-branches.rst index 1b2fc12..d295b64 100644 --- a/doc/source/stable-branches.rst +++ b/doc/source/stable-branches.rst @@ -222,7 +222,7 @@ branches which generally includes: backports from passing tests. These could be project-specific or global in nature and are usually tracked in the `stable tracker etherpad`_. From time to time the Stable Maintenance Core team may also ask for help from - individual projects in IRC or the openstack-dev mailing list and expect a + individual projects in IRC or the openstack-discuss mailing list and expect a reasonably prompt response. .. note:: @@ -254,7 +254,7 @@ Some types of changes are completely forbidden: * Incompatible config file changes Proposed backports breaking any of the above guidelines can be discussed as -exception requests on the openstack-dev list (prefix with [stable]) where +exception requests on the openstack-discuss list (prefix with [stable]) where the stable maintenance core team will have the final say. Each backported commit proposed to Gerrit should be reviewed and +2ed by