Skip to content

Commit b94a3a8

Browse files
authored
Merge pull request #1350 from bashirk/bashirk-maintainer-faq
2 parents 156a9bf + 6aa450e commit b94a3a8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/maintainer/maintainer_faq.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ FAQ
1717
Exited with code 128
1818

1919
open a new issue with a comment :ref:`ci_update_circle`.
20-
Once our web services updated the circle configuration, restart the build.
20+
Once our web services have updated the circle configuration, restart the build.
2121

2222

2323
.. _mfaq_py37_selector:
@@ -28,7 +28,7 @@ FAQ
2828

2929
conda-build has changed the selector syntax.
3030
You are now encouraged to use ``py==<version>``, instead of ``py<version>``.
31-
While the legacy selectors ``py27`` and ``py36`` are still valid, ``py37`` and higher are not available anymore.
31+
While the legacy selectors ``py27`` and ``py36`` are still valid, selectors ``py37`` and higher are no longer valid.
3232

3333
Please use the new syntax ``py==27``, ``py==36`` and ``py==37`` to avoid confusion.
3434

@@ -44,7 +44,7 @@ FAQ
4444

4545
TL;DR: there is no need for build numbers larger than 1000 anymore.
4646

47-
When you update a feedstock that still uses build numbers > 1000, following rules apply:
47+
When you update a feedstock that still uses build numbers > 1000, the following rules apply:
4848

4949
- when you increase the version, reset the build number back to 0 (e.g. ``1005 -> 0``).
5050
- when the version stays the same and you need to upload a new package, increase the build number by 1 (e.g. ``1005 -> 1006``).
@@ -67,4 +67,4 @@ FAQ
6767

6868
:ref:`(Q) <mfaq_anaconda_delay>` **Why does my new version appear on Anaconda Cloud, but is not installable with conda?**
6969

70-
For certain, high-traffic channels (main & conda-forge), Anaconda uses a CDN to decrease costs. The CDN is only reindexed every 20 min, however Anaconda.org uses the original channel that the CDN mirrors. Therefore, packages will show up on the anaconda.org ~20-40 min before they are downloadable by conda. You can use conda search <pkg> to see if the package is installable, because this command reads from the CDN.
70+
For certain, high-traffic channels (main & conda-forge), Anaconda uses a `CDN <https://cloudflare.com/learning/cdn/what-is-a-cdn/>`_ to decrease costs. The CDN is only reindexed every 20 minutes, however `Anaconda.org https://anaconda.org>`_ uses the original channel that the CDN mirrors. Therefore, packages will show up on the `Anaconda Cloud https://anaconda.org>`_ about 20 to 40 minutes before they are downloadable via conda. You can use ``conda search <pkg>`` to see if the package is installable, because this command reads from the CDN.

0 commit comments

Comments
 (0)