Merge pull request #1980 from conda-forge/rhel6-eol

ENH set date for cos6 EOL

Author: beckermr

src/maintainer/knowledge_base.rst

@@ -1132,7 +1132,7 @@ In order to qualify as a noarch python package, all of the following criteria mu
   ``dataclasses``.
 
 .. hint::
-  
+
   You can build platform-specific ``noarch`` packages to include runtime requirements depending on the target OS.
   See mini-tutorial below.
 
@@ -1148,7 +1148,7 @@ It is possible to build ``noarch`` packages with runtime requirements that depen
 (Linux, Windows, MacOS), regardless the architecture (amd64, ARM, PowerPC, etc). This approach
 relies on three concepts:
 
-1.  `Virtual packages <https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-virtual.html>`__. 
+1.  `Virtual packages <https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-virtual.html>`__.
     Prefixed with a double underscore, they are used by conda to represent system properties as
     constraints for the solver at install-time. We will use ``__linux``, ``__win`` or ``__osx``,
     which are only present when the running platform is Linux, Windows, or MacOS, respectively.
@@ -1826,7 +1826,7 @@ If you close the PR, it makes the bot think that another PR implementing the mig
 Another reason why it is good to keep the PR open or in draft status is that people might help with it if they want in the future.
 
 In some cases a migration PR may not get opened. Please look for
-`the migration on our status page <https://conda-forge.org/status/#current_migrations>`_
+`the migration on our status page <https://conda-forge.org/status/#big_migrations>`_
 to see if there are any issues. This may show there are still dependencies
 needing migration, in which case the best approach is to wait (or if possible
 offer to help migrate those dependencies). If there is a bot error, there will

src/maintainer/updating_pkgs.rst

@@ -68,7 +68,7 @@ When a new version of a package is released on PyPI/CRAN/.., we have a bot that
 The `regro-cf-autotick-bot <https://github.com/regro/autotick-bot>`__ continuously searches on a loop for any PyPI releases, GitHub releases, and any other sources of versions when any updates are released. The source code that gets executed in the loop comes from the `cf-scripts repository <https://github.com/regro/cf-scripts>`__, which contains the code to detect versions and submit PRs. Visit `cf-scripts <https://regro.github.io/cf-scripts/index.html>`__ to read more about it.
 
 The bot creates updates via inspection of the upstream release and will always update the ``source`` section and build version in the `recipe metadata <https://docs.conda.io/projects/conda-build/en/stable/resources/define-metadata.html#>`_.
-As an experimental feature, the autotick bot can also be configured to verify or update the recipe's requirements for `Grayskull <https://github.com/conda-incubator/grayskull>`_-compatible recipes. 
+As an experimental feature, the autotick bot can also be configured to verify or update the recipe's requirements for `Grayskull <https://github.com/conda-incubator/grayskull>`_-compatible recipes.
 This may help maintain packages with frequent requirements changes or specific requirements version pins, however this feature is not as extensively verified and proposed updates should be reviewed.
 (See the :ref:`bot` section in ``conda-forge.yml``)
 
@@ -174,7 +174,7 @@ Updating for newly released Python version
 ==========================================
 
 When a new Python version is released (e.g. ``3.11``), an automatic migration process is triggered that will have ``@regro-cf-autotick-bot`` eventually automatically open pull requests to all feedstocks, updating their CI setup to include the new Python version in the build matrix. After veryfing that the PR build passes, that automatic PR can simply be merged to roll out packages for new Python version.
-This process takes time, though, and pull requests will not be opened to all feedstocks at the same time to not overload CI. The current status of the migration can be tracked on the `migration status page <https://conda-forge.org/status/#current_migrations>`_ and there maintainers can verify that their feedstock is listed under the ``AWAITING-PR`` dropdown list.
+This process takes time, though, and pull requests will not be opened to all feedstocks at the same time to not overload CI. The current status of the migration can be tracked on the `migration status page <https://conda-forge.org/status/#big_migrations>`_ and there maintainers can verify that their feedstock is listed under the ``AWAITING-PR`` dropdown list.
 
 Testing changes locally
 =======================
@@ -247,7 +247,7 @@ the `repo data patches feedstock <https://github.com/conda-forge/conda-forge-rep
 If this is the case, the following general guidelines should be followed:
 1. Update the feedstocks recipe to ensure future builds do not propagate the issue with a new build number.
 2. Please make a PR there to add a patch. The patch should specify as much has possible the versions and times when the packages were generated. It may use the following information
-   
+
    - The current timestamp, you may generate it with ``python -c "import time; print(f'{time.time():.0f}000')"``.
    - The problematic version and build numbers of the packages to affect.
 
@@ -285,7 +285,7 @@ an issue in the feedstock repository with the following title:
 ``@conda-forge-admin, please add user @username``
 
 where ``username`` is the username of the new maintainer to be added.
-A PR will be automatically created and a maintainer or a member of the ``core`` team, in case no maintainer is active anymore, can then merge this PR to add the user. 
+A PR will be automatically created and a maintainer or a member of the ``core`` team, in case no maintainer is active anymore, can then merge this PR to add the user.
 To contact core, ping them by mentioning @conda-forge/core in a comment or, if you haven't heard back in a while or are new to conda-forge, contact them through the community `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 
 .. note::

src/user/announcements.rst

@@ -8,20 +8,31 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
 2023
 ----
 
+2023-07-12: End-of-life for CentOS 6
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+As you may be aware, we have delayed the deprecation of our CentOS 6 build
+system the ``linux64`` platform several times. We have now set a formal deprecation
+date to be June 30, 2024. This date matches the
+`end of extended life-cycle support <https://endoflife.software/operating-systems/linux/red-hat-enterprise-linux-rhel>`_
+from RedHat for RHEL 6. After this date, we build packages against
+CentoOS 7 by default for ``linux64``.
+
+
 2023-01-09: conda-forge Google Group is Now Read-only - Move to Discourse
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-We have made the conda-forge Google Group read-only. Please use the new 
-conda-forge `discourse forum <https://conda.discourse.group/c/pkg-building/conda-forge/25>`_, 
-our `Gitter room <https://gitter.im/conda-forge/conda-forge.github.io>`_, or it's `Matrix/Element 
+We have made the conda-forge Google Group read-only. Please use the new
+conda-forge `discourse forum <https://conda.discourse.group/c/pkg-building/conda-forge/25>`_,
+our `Gitter room <https://gitter.im/conda-forge/conda-forge.github.io>`_, or it's `Matrix/Element
 counterpart <https://app.element.io/#/room/#conda-forge-space:matrix.org>`_ instead.
 
 
 2023-01-08: ``conda-forge/staged-recipes`` Feedstock Creation Job Moved
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-We have moved the CI job that makes new feedstocks to our 
-`conda-forge/admin-requests <https://github.com/conda-forge/admin-requests>`_ 
+We have moved the CI job that makes new feedstocks to our
+`conda-forge/admin-requests <https://github.com/conda-forge/admin-requests>`_
 repo. The new location is reflected in the various links on repos and our status page.
 
 2022