|
| 1 | +--- |
| 2 | +authors: |
| 3 | + - core |
| 4 | +tags: [conda-forge] |
| 5 | +--- |
| 6 | + |
| 7 | +# 2020 in Review |
| 8 | + |
| 9 | +As 2020 winds down, the Core team thought it'd be fun to review some of |
| 10 | +the big accomplishments our community has made this year. |
| 11 | + |
| 12 | +## Strong Growth |
| 13 | + |
| 14 | +The `conda-forge` community has grown immensely this year. Here are some |
| 15 | +numbers to help give you an idea of the scale of our growth. |
| 16 | + |
| 17 | +- The community has added 3,751 new, unique `conda` packages this |
| 18 | + year, along with a corresponding number of new feedstocks. |
| 19 | +- For the majority of 2020, the `conda-forge` channel on |
| 20 | + `anaconda.org` exceeded 100 million downloads per month. |
| 21 | +- In July of 2020, the `conda-forge` channel passed 2 billion total, |
| 22 | + all-time downloads. |
| 23 | +- We've grown our core developer community, adding seven new members |
| 24 | + to the `conda-forge` Core team and at least two members to the |
| 25 | + `staged-recipes` team. |
| 26 | +- We now have over 2,500 recipe maintainers in the `conda-forge` |
| 27 | + GitHub organization. |
| 28 | + |
| 29 | +## Big New Features |
| 30 | + |
| 31 | +We've also shipped a ton of big updates to our core infrastructure this |
| 32 | +year. These updates include |
| 33 | + |
| 34 | +- `PyPy` **support**: We added support for `PyPy` 3.6 and now supply |
| 35 | + one of the biggest stacks of `PyPy`-enabled packages in the `PyPy` |
| 36 | + ecosystem. |
| 37 | +- **automerge**: We now support the automatic merging of PRs on |
| 38 | + feedstocks using the `automerge` label or through an opt-in setting |
| 39 | + in the `conda-forge.yml`. |
| 40 | +- `R` **4.0 migration**: This migration was the first one to use our |
| 41 | + `automerge` infrastructure at scale. With it, we completed a |
| 42 | + complete rebuild/upgrade of the `R` ecosystem in about a week. |
| 43 | +- `Python` **updates**: We deprecated `Python` 2.7, completed the |
| 44 | + `Python` 3.8 migration, and got about 75% of the way through the |
| 45 | + `Python` 3.9 migration. |
| 46 | +- **compiler upgrades**: We upgraded our compiler infrastructure to |
| 47 | + `GCC` 9 and `clang` 11. |
| 48 | +- **CentOS 7 and CentOS 6 EOL**: We shipped an option to enable our |
| 49 | + compilers to use the CentOS 7 `sysroot` in preparation for the |
| 50 | + CentOS 6 EOL. We hope to complete the move to CentOS 7 early next |
| 51 | + year. |
| 52 | +- **miniforge**: We built our own standalone, `miniconda`-like |
| 53 | + installers. These support a broad range of platforms, including |
| 54 | + `osx-arm64` and `linux-aarch64`. |
| 55 | +- **standalone Windows stack**: We fully decoupled our Windows recipes |
| 56 | + from the `defaults` channel by rebuilding the `msys2` recipes. |
| 57 | +- **Apple silicon support**: We added support for Apple silicon with |
| 58 | + our `osx-arm64` platform. This platform is our first one to use a |
| 59 | + fully cross-compiled infrastructure. |
| 60 | +- **CUDA support**: We added support for building CUDA packages on |
| 61 | + windows and added CUDA 11.0 support. |
| 62 | + |
| 63 | +------------------------------------------------------------------------ |
| 64 | + |
| 65 | +We know that this year has been extremely difficult for so many of our |
| 66 | +community members and that the fantastic success of `conda-forge` would |
| 67 | +not have been possible without the active participation and support of |
| 68 | +our community. **Thank you everyone so much for the work you put into** |
| 69 | +`conda-forge` **this year, making it the wonderful, community-led |
| 70 | +resource that it is.** |
| 71 | + |
| 72 | +We wish everyone a happy, healthy, and peaceful new year! |
0 commit comments