Initial draft of conda-libmamba-solver rollout blogpost.

blog/2023-06-10-conda-libmamba-solver-rollout.mdx

@@ -0,0 +1,42 @@
+---
+title: "Conda and the libmamba solver: Roll-out plan 2023"
+slug: "2023-06-10-conda-libmamba-solver-rollout"
+description: |
+    Learn about the upcoming rollout plan for the conda-libmamba-solver, bringing enhanced performance and user experience to conda.
+authors: [jezdez]
+tags: [conda, mamba, solver, libmamba, dependency solver, performance, user experience, conda-forge, pycosat, plugin package, Anaconda Distribution, miniconda, CEP 8, CEP 9]
+
+---
+## Background
+
+
+Over a year ago, the conda team at Anaconda, together with conda developers at Quansight and QuantStack, [announced the release](https://www.anaconda.com/blog/a-faster-conda-for-a-growing-community) of a new solver for conda based on the solver that the [mamba project](https://mamba.readthedocs.io/) had developed on top of the venerable libsolv project.
+
+The dependency solver is one of the main pillars that makes up the conda package and environment manager (next to the network & IO stack and the command line interface integration, for example) and has been the source of many performance and user experience issues over the years, given the growth of the conda ecosystem. Users of conda-forge and other larger conda channels in particular struggled with the current solver implementation based on pycosat.
+
+[Fast-forward to December 2022](https://www.anaconda.com/blog/conda-is-fast-now); we’ve encouraged the use of the libmamba solver via the separate plugin package “conda-libmamba-solver" as a way to trial the use of the solver and get more feedback from real-world users. In case you haven't had the chance to provide your feedback, please head over to the [conda-libmamba-solver repository on GitHub](https://github.com/conda/conda-libmamba-solver).
+
+## Roll-out Plan
+
+
+We're happy to announce the roll-out plan for the next phase for the solver, which we’re starting to implement to get the conda-libmamba-solver in the hands of more people.
+
+The June 2023 editions of the [Anaconda Distribution](https://www.anaconda.com/download/) and [miniconda](https://docs.conda.io/en/latest/miniconda.html) installers will include the [conda-libmamba-solver](https://conda.github.io/conda-libmamba-solver/) package by default for new installations.
+
+This will make switching to the solver much easier for end users, as it will require only setting `CONDA_SOVLER=libmamba` (for one-time runs) or `conda config --set solver=libmamba` (for persistently switching via the `.condarc` file) and not require additional installation steps. More details on that in the [conda-libmamba-solver getting started guide](https://conda.github.io/conda-libmamba-solver/getting-started/).
+
+We expect many more users to try it out that way to get more feedback where we can improve it further. If you’d like to send us your feedback now, please don’t hesitate to open a ticket in the [conda](https://github.com/conda/conda/issues/new/choose) and [conda-libmamba-solver](https://github.com/conda/conda-libmamba-solver/issues/new/choose) repositories on GitHub accordingly.
+
+## Changing the default solver
+
+
+Afterwards, in the September 2023 release window for conda (`23.9.0` per [CEP 8](https://github.com/conda-incubator/ceps/blob/main/cep-8.md)), we'll also:
+
+
+- switch the default solver configuration to `libmamba`(no need to `--solver=libmamba` anymore)
+- keep the `classic` solver code included in conda, to be able to "switch back”, if circumstances require it, via `--solver=classic` and
+- create a plan to retire the `classic` solver in the far-future.
+
+The long-term plan for the `classic` solver will include a timeline for deprecation from the main conda code base based on [CEP 9](https://github.com/conda-incubator/ceps/blob/main/cep-9.md) and additional public discussions with users if it's worth keeping the solver maintained in a separate conda plugin package (for example).
+
+We understand that there are users who have built their workflows around the classic solver, and we want to provide ample time and support for them to migrate to the new solver. In case you have any input on our plans, please let us know! We look forward to working closely with the rest of the conda community to ensure a smooth transition.

blog/authors.yml

@@ -24,6 +24,11 @@ jaimergp:
   title: Steering council member
   url: https://github.com/jaimergp
   image_url: https://github.com/jaimergp.png
+jezdez:
+  name: Jannis Leidel
+  title: Steering council member
+  url: https://github.com/jezdez
+  image_url: https://github.com/jezdez.png
 tnabtaf:
   name: Dave Clements
   title: Open Source Community Manager