Skip to content

Commit dc805ec

Browse files
committed
DOC update language a bit
1 parent 224c434 commit dc805ec

File tree

1 file changed

+12
-11
lines changed

1 file changed

+12
-11
lines changed

src/user/announcements.rst

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,18 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
88
2020
99
----
1010

11-
:2020-12-16: Moving to CentOS7 and CentOS6 End-of-Life
12-
13-
``conda-forge``'s compiler stack uses repackaged libraries from CentOS6
14-
    to supply certain libraries, notably ``glibc`` when building recipes. We currently
15-
    default to using CentOS6 with the ``glibc`` 2.12 ABI. However, CentOS6 reached
16-
    end-of-life in November 2020 and increasingly software packages require at
17-
    least CentOS7 with the ``glibc`` 2.17 ABI. We also realize that some
18-
    communities who may have been planning to skip CentOS7 and move straight to
19-
CentOS8 might not be ready for a full-scale switch to CentOS7. Thus the
20-
``conda-forge`` core team has decided to delay moving to CentOS7 until sometime
21-
early next year, likely the end of January 2021 at the earliest. We are actively
11+
:2020-12-16: Moving to CentOS 7 and CentOS 6 End-of-Life
12+
13+
``conda-forge``'s compiler stack uses repackaged libraries from CentOS 6
14+
to supply certain libraries, notably ``glibc`` when building recipes. We currently
15+
default to using CentOS 6 with the ``glibc`` 2.12 ABI. However, CentOS6 reached
16+
end-of-life in November 2020 and increasingly software packages require at
17+
least CentOS 7 with the ``glibc`` 2.17 ABI. We also realize that due to recent
18+
events some communities that may have been planning to skip CentOS 7
19+
and move straight to CentOS 8 might be reconsidering those plans. Further, they
20+
may not be ready for a full-scale switch to CentOS 7. Thus the
21+
``conda-forge`` core team has decided to delay moving to CentOS 7 until sometime
22+
early next year, likely the end of January 2021 at the earliest. We are actively
2223
looking for feedback from our users on this issue. Please do :ref:`get in touch <getintouch>`
2324
if you have comments or concerns!
2425

0 commit comments

Comments
 (0)