Update for openstack-dev move

Update text to use openstack-discuss instead of openstack-dev.

Change-Id: I569f5b42fc20c1ea8926ba7e1543a598a705ae73

security-guide/source/compute/hardening-deployments.rst

@@ -70,18 +70,16 @@ current set of OSSNs is in the `Security Note wiki
 OpenStack-dev mailinglist
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-All bugs, OSSAs and OSSNs are publicly disseminated through the openstack-dev
+All bugs, OSSAs and OSSNs are publicly disseminated through the
+openstack-discuss
 mailinglist with the [security] topic in the subject line. We recommend
 subscribing to this list as well as mail filtering rules that ensure OSSNs,
-OSSAs, and other important advisories are not missed. The openstack-dev
+OSSAs, and other important advisories are not missed. The openstack-discuss
 mailinglist is managed through
 `OpenStack Development Mailing List
-<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>`_.
-The openstack-dev list has a high traffic rate, and filtering is discussed in
-the thread
-`filtering traffic on the mailing list
-<http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html>`_.
-
+<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss>`_.
+The openstack-discuss uses tags as defined in
+the `Project Team Guide <https://docs.openstack.org/project-team-guide/open-community.html#mailing-lists>`_.
 
 Hypervisor mailinglists
 ~~~~~~~~~~~~~~~~~~~~~~~

security-guide/source/compute/vulnerability-awareness.rst

@@ -31,20 +31,18 @@ Bashbug/Ghost or Venom vulnerabilities that affect the platform OpenStack
 utilizes. The current set of OSSNs is in the `Security Note wiki
 <https://wiki.openstack.org/wiki/Security_Notes>`_.
 
-OpenStack-dev mailing list
-~~~~~~~~~~~~~~~~~~~~~~~~~~
+OpenStack-discuss mailing list
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-All bugs, OSSAs and OSSNs are publicly disseminated through the openstack-dev
+All bugs, OSSAs and OSSNs are publicly disseminated through the openstack-discuss
 mailing list with the [security] topic in the subject line. We recommend
 subscribing to this list as well as mail filtering rules that ensure OSSNs,
-OSSAs, and other important advisories are not missed. The openstack-dev
+OSSAs, and other important advisories are not missed. The openstack-discuss
 mailinglist is managed through
-`http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>`_.
-The openstack-dev list has a high traffic rate, and filtering is discussed in
-the thread
-`http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html
-<http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html>`_.
+`http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
+<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss>`_.
+The openstack-discuss uses tags as defined in
+the `Project Team Guide <https://docs.openstack.org/project-team-guide/open-community.html#mailing-lists>`_.
 
 Hypervisor mailinglists
 ~~~~~~~~~~~~~~~~~~~~~~~

security-guide/source/index.rst

@@ -22,7 +22,7 @@ securing an OpenStack cloud.
    The OpenStack Security team is based on voluntary contributions
    from the OpenStack community. You can contact the security community
    directly in the #openstack-security channel on Freenode IRC, or by
-   sending mail to the openstack-dev mailing list with the
+   sending mail to the openstack-discuss mailing list with the
    [security] prefix in the subject header.
 
 Contents

security-notes/template.txt

@@ -22,6 +22,6 @@ example snippets of configuration files should be included here.
 Author: <author name(s) and company(s)>
 This OSSN : <link to OSSN on wiki>
 Original LaunchPad Bug : <link to launchpad bug for affected project/service>
-Mailing List : [Security] tag on openstack-dev@lists.openstack.org
+Mailing List : [Security] tag on openstack-discuss@lists.openstack.org
 OpenStack Security Project : https://launchpad.net/~openstack-ossg
 CVE: <CVE number if one was filed>

security-threat-analysis/setup.cfg

@@ -2,7 +2,7 @@
 name = openstacksecurityguide
 summary = OpenStack Security Guide
 author = OpenStack
-author-email = openstack-dev@lists.openstack.org
+author-email = openstack-discuss@lists.openstack.org
 home-page = http://docs.openstack.org/
 classifier =
 Environment :: OpenStack

security-threat-analysis/source/threat-analysis-process.rst

@@ -19,7 +19,7 @@ Preparing artifacts for review
   provided at :ref:`architecture-page` and there is guidance on
   diagramming at :ref:`architecture-diagram-guidance`. If further help or
   advice is needed, please reach out to the Security Project via the
-  openstack-dev@lists.openstack.org mailing list, tagging your email
+  openstack-discuss@lists.openstack.org mailing list, tagging your email
   [security].
 - The architecture page should describe a best practice deployment. If a
   reference architecture is available this may be a good example to use,
@@ -45,8 +45,8 @@ Before the review
   listed in the Architecture Page Template :ref:`architecture-page`.
 - The architecture page should include diagrams as specified in the
   Architecture Diagram guidance :ref:`architecture-diagram-guidance`.
-- Send an email to the openstack-dev@lists.openstack.org mailing list with a
-  [security] tag to announce the up-coming threat analysis review.
+- Send an email to the openstack-discuss@lists.openstack.org mailing
+  list with a [security] tag to announce the up-coming threat analysis review.
 - Prepare a threat analysis review etherpad, using this template <link>.
 - Print the architecture page as a PDF, to be checked in along with the review
   notes, as evidence of what was reviewed.