Commit 5709bb8b authored by Tristan van Berkom's avatar Tristan van Berkom

All: Update all references to the mailing list.

Update any references to the mailing list to now point to:[email protected]
parent c310f203
Pipeline #162738860 passed with stages
in 49 minutes and 22 seconds
......@@ -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="" />
<mailing-list rdf:resource="" />
<mailing-list rdf:resource="[email protected]" />
<download-page rdf:resource="" />
<bug-database rdf:resource="" />
......@@ -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
<[email protected]>`_
before being considered for inclusion. To save time and avoid any frustration,
we strongly recommend proposing your new feature in advance of commencing work.
......@@ -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
<>`_. Chances
<[email protected]>`_. 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
......@@ -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 ``[email protected]`` and
to ``[email protected]``.
* Ability to send email to ``[email protected]``.
* Shell account at ````.
......@@ -113,9 +112,9 @@ Release process
announcements as much as possible, an example of the email
can be `found here <>`_.
The recipients of the email are ``[email protected]`` and
``[email protected]`` 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 ``[email protected]`` 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 <>`_,
`in the mailing list archives <[email protected]/>`_,
and use that URL to update the ``anouncements.json`` file in the website
......@@ -320,7 +320,7 @@ setup(
author="BuildStream Developers",
author_email="[email protected]",
author_email="[email protected]",
"Environment :: Console",
"Intended Audience :: Developers",
......@@ -341,7 +341,7 @@ setup(
"Source": "",
"Documentation": "",
"Tracker": "",
"Mailing List": "",
"Mailing List": "[email protected]",
python_requires="~={}.{}".format(REQUIRED_PYTHON_MAJOR, REQUIRED_PYTHON_MINOR),
package_dir={"": "src"},
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment