diff options
| author | Tristan van Berkom <tristan.vanberkom@codethink.co.uk> | 2020-07-03 16:02:15 +0900 |
|---|---|---|
| committer | Tristan van Berkom <tristan.vanberkom@codethink.co.uk> | 2020-07-03 16:03:41 +0900 |
| commit | 5709bb8b76dcce4b9ecd08842c20efc1aa043aee (patch) | |
| tree | 2730cf3b217b0119f3867c572b25257926bc2b0f /doc | |
| parent | c310f20363eb92f77f7db7d841b1bf99eae0b122 (diff) | |
| download | buildstream-5709bb8b76dcce4b9ecd08842c20efc1aa043aee.tar.gz | |
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
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/hacking/coding_guidelines.rst | 2 | ||||
| -rw-r--r-- | doc/source/hacking/making_releases.rst | 11 |
2 files changed, 6 insertions, 7 deletions
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. |