-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add announcement about miniconda & mambaforge unification #1995
Conversation
I wonder if we should provide more info on why we decided to do this that may answer some questions. Trying to put myself on the shoes of a user here I guess that they could ask:: Why the unification? Should I choose one or another going forward at the risk of one of them getting deprecated? If I used mini/mamba-forge am I wasting/saving space by getting more/less? |
Thanks @ocefpaf! Let me answer inline and then we can decide if the info is worth sharing in the announcement or maybe a FAQ section in conda-forge.org/miniforge.
Miniforge is a conda-forge-based, Miniconda-like installer. It has historically tried to provide the same components. Miniconda started shipping conda-libmamba-solver in July, in preparation for the default solver switch in September. Bundling conda-libmamba-solver implies pulling the Since the installer size difference is now moot, we decided to go ahead and merge both for simplicity and "less surprising" behavior.
There are no concrete plans to deprecate any or the other. That said, if you were to ask me, I'd keep Miniforge and eventually deprecate Mambaforge. If we ever decide to do so (which might break too many unattended setups), it will be properly announced, with deprecation warnings and brown-outs or whatever we come up with.
If you were using Mambaforge already, this change won't have any perceivable effects. If you were stuck with Miniforge, this release opens up new fast solver possibilities, at the cost of some megabytes. It shouldn't be that terrible (~20MB in installer size for Linux x64). |
Indeed that is the info some users may be after. I'm not sure if it is too verbose for that announcement or if it should be there. To be honest, I'm on the fence, but I know those things and the user reading the announcement may not. |
I added conda-forge/miniforge#478 so we can link to the FAQ section of the Miniforge repo. |
- ``conda-libmamba-solver`` (23.3.0 in this release) | ||
- ``mamba`` (1.4.2 in this release) | ||
- ... plus their dependencies | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would only add a note that we are discouraging the use of Mambaforge
- ``mamba`` (1.4.2 in this release) | ||
- ... plus their dependencies | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have decided to keep the download links | |
of Mambaforge active to help those that have automated workflows. | |
The new usage of Mambaforge is thus discouraged. Bug | |
reports specific to Mambaforge will be closed as won't fix. |
PR Checklist:
xrefs:
conda-libmamba-solver
miniforge#284