Skip to content

Commit cff6f9e

Browse files
Hugo's other suggestions
1 parent de20eb1 commit cff6f9e

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

testing/buildbots.rst

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,9 @@ In case of trouble
3333
Please read this page in full. If your questions aren't answered here and you
3434
need assistance with the buildbots, a good way to get help is to either:
3535

36-
* contact the ``python-buildbots@python.org`` mailing list where all buildbot
37-
worker owners are subscribed; or
36+
* contact the `python-buildbots@python.org
37+
<https://mail.python.org/archives/list/python-buildbots@python.org/>`_
38+
mailing list where all buildbot worker owners are subscribed; or
3839
* contact the release manager of the branch you have issues with.
3940

4041

@@ -72,7 +73,7 @@ one or more buildbots by posting a comment that begins with:
7273
7374
!buildbot regex-matching-target
7475
75-
For example to run both the iOS and Android build bot, you can use:
76+
For example to run both the iOS and Android buildbots, you can use:
7677

7778
.. code-block:: none
7879
@@ -93,7 +94,7 @@ Checking results of automatic builds
9394
The Web interface at https://buildbot.python.org/#/ has several ways of
9495
visualizing recent build results:
9596

96-
* A `Release Status Dashboard <https://buildbot.python.org/#/release_status>`_
97+
* A `release status dashboard <https://buildbot.python.org/#/release_status>`__
9798
that shows the status of buildbots for each active branch,
9899
summarizing whether the builds are ready for release.
99100

@@ -126,10 +127,10 @@ Stability
126127
A subset of the buildbots are marked as
127128
`"stable" <https://buildbot.python.org/#/builders?tags=%2Bstable>`__.
128129
They are taken into account when making a new release.
129-
The rule is that all stable builders must be free of
130-
persistent failures when the release is cut. It is absolutely **vital**
131-
that core team members fix or revert any issue they introduce on the stable
132-
buildbots, as soon as possible.
130+
The rule is that all tier 1 and 2 stable builders must be free of
131+
persistent failures when the release is cut (see :pep:`11` for more information).
132+
It is absolutely **vital** that core team members fix or revert any issue they
133+
introduce on the stable buildbots, as soon as possible.
133134

134135
This does not mean that other builders' test results can be taken lightly,
135136
either. Some of them are known for having platform-specific issues that

0 commit comments

Comments
 (0)