All: Update all references to the mailing list.

Update any references to the mailing list to now point to:

    https://lists.apache.org/list.html?dev@buildstream.apache.org

5 files changed, 10 insertions, 11 deletions

diff --git a/BuildStream.doap b/BuildStream.doap
index 263ded41e..15894b2ab 100644
--- a/BuildStream.doap
+++ b/BuildStream.doap
@@ -8,7 +8,7 @@
   <name xml:lang="en">BuildStream</name>
   <shortdesc xml:lang="en">Build tool for running abstract, deterministic build pipelines</shortdesc>
   <homepage rdf:resource="https://gitlab.com/BuildStream/buildstream/" />
-  <mailing-list rdf:resource="https://mail.gnome.org/mailman/listinfo/buildstream-list" />
+  <mailing-list rdf:resource="https://lists.apache.org/list.html?dev@buildstream.apache.org" />
   <download-page rdf:resource="http://download.gnome.org/sources/BuildStream/" />
   <bug-database rdf:resource="https://gitlab.com/BuildStream/buildstream/issues" />
 
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index cbf99367f..b03388ef1 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -29,7 +29,7 @@ Patches which fix bugs should always come with a regression test.
 Adding new features
 -------------------
 Feature additions should be proposed on the `mailing list
-<https://mail.gnome.org/mailman/listinfo/buildstream-list>`_
+<https://lists.apache.org/list.html?dev@buildstream.apache.org>`_
 before being considered for inclusion. To save time and avoid any frustration,
 we strongly recommend proposing your new feature in advance of commencing work.
 
diff --git a/doc/source/hacking/coding_guidelines.rst b/doc/source/hacking/coding_guidelines.rst
index bdc568c9d..0ac3bf923 100644
--- a/doc/source/hacking/coding_guidelines.rst
+++ b/doc/source/hacking/coding_guidelines.rst
@@ -675,7 +675,7 @@ than the actual way in which things are done, always.
 
 Instead, if you like a certain Python feature and think the BuildStream
 codebase should use it, then propose your change on the `mailing list
-<https://mail.gnome.org/mailman/listinfo/buildstream-list>`_. Chances
+<https://lists.apache.org/list.html?dev@buildstream.apache.org>`_. Chances
 are that we will reach agreement to use your preferred approach, and
 in that case, it will be important to apply the change unilaterally
 across the entire codebase, such that we continue to have a consistent
diff --git a/doc/source/hacking/making_releases.rst b/doc/source/hacking/making_releases.rst
index a877b1fa4..d9d34ae32 100644
--- a/doc/source/hacking/making_releases.rst
+++ b/doc/source/hacking/making_releases.rst
@@ -14,8 +14,7 @@ Requirements
 There are a couple of requirements and accounts required in order
 to publish a release.
 
-* Ability to send email to ``buildstream-list@gnome.org`` and
-  to ``gnome-announce-list@gnome.org``.
+* Ability to send email to ``dev@buildstream.apache.org``.
 
 * Shell account at ``master.gnome.org``.
 
@@ -113,9 +112,9 @@ Release process
   announcements as much as possible, an example of the email
   can be `found here <https://mail.gnome.org/archives/buildstream-list/2019-February/msg00039.html>`_.
 
-  The recipients of the email are ``buildstream-list@gnome.org`` and
-  ``gnome-announce-list@gnome.org`` and the title of the email should
-  be of the form: ``BuildStream 1.1.1 released``, without any exclamation point.
+  The recipient of the email is ``dev@buildstream.apache.org`` and the title
+  of the email should be of the form: ``BuildStream 1.1.1 released``, without
+  any exclamation point.
 
   The format of the email is essentially::
 
@@ -237,7 +236,7 @@ which need to be done to ensure everything is up to date.
   the release email will be in the mailing list archive.
 
   Find the URL to the announcement you just published
-  `in the mailing list archives <https://mail.gnome.org/archives/buildstream-list/>`_,
+  `in the mailing list archives <https://lists.apache.org/list.html?dev@buildstream.apache.org/>`_,
   and use that URL to update the ``anouncements.json`` file in the website
   repository.
 
diff --git a/setup.py b/setup.py
index 3387053a0..c300d33e9 100755
--- a/setup.py
+++ b/setup.py
@@ -320,7 +320,7 @@ setup(
     version=versioneer.get_version(),
     cmdclass=get_cmdclass(),
     author="BuildStream Developers",
-    author_email="buildstream-list@gnome.org",
+    author_email="dev@buildstream.apache.org",
     classifiers=[
         "Environment :: Console",
         "Intended Audience :: Developers",
@@ -341,7 +341,7 @@ setup(
         "Source": "https://gitlab.com/BuildStream/buildstream",
         "Documentation": "https://docs.buildstream.build",
         "Tracker": "https://gitlab.com/BuildStream/buildstream/issues",
-        "Mailing List": "https://mail.gnome.org/mailman/listinfo/buildstream-list",
+        "Mailing List": "https://lists.apache.org/list.html?dev@buildstream.apache.org",
     },
     python_requires="~={}.{}".format(REQUIRED_PYTHON_MAJOR, REQUIRED_PYTHON_MINOR),
     package_dir={"": "src"},