Skip to content

Commit

Permalink
link to announcement
Browse files Browse the repository at this point in the history
  • Loading branch information
jaimergp committed Sep 15, 2024
1 parent 0cd2be4 commit 6815a9a
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions docs/user/transitioning_from_defaults.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,9 +122,9 @@ You should now be in a position to use conda-forge packages.
## A historical note

Until roughly 2021, conda-forge held strong compatibility with Anaconda's
default channel. However, due to the reasons outlined in XXXXXX, we decided to
ultimately move away from dependency on Anaconda's `defaults` packages. Over the
years, this has led for more divergence between package versions, and names
default channel. However, as [announced in September 2021][defaults-announcement],
we decided toultimately move away from dependency on Anaconda's `defaults` packages.
Over the years, this has led for more divergence between package versions, and names
between conda-forge and Anaconda's `defaults` channel.
In 2024, the workflow that has packages co-installed from Anaconda's channel and
Expand All @@ -140,3 +140,5 @@ All packages should specify that they have been installed from the conda-forge
channel. In 2024, there still exist a few bugs where conda packages will
claim that they have been installed from PyPI even though they have been
installed from conda-forge.

[defaults-announcement]: /news/2021/09/30/defaults-channel-is-now-dropped-when-building-conda-forge-packages/

0 comments on commit 6815a9a

Please sign in to comment.