Skip to content
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

Start deprecation of miniforge-variant: Mambaforge #360

Merged
merged 4 commits into from
Jul 30, 2024
Merged

Conversation

jaimergp
Copy link
Member

Comes from conda-forge/miniforge#602

Mambaforge and Miniforge are equivalent these days. Maintaining Mambaforge adds unnecessary burden on the Miniforge repo and creates confusion for end users. We'd like to sunset it eventually, and to do so we are starting the deprecation cycle with a warning.

@jaimergp
Copy link
Member Author

Thanks @dbast!

I'd wait til conda-forge/conda-forge.github.io#2242 is published, then we can merge.

@jaimergp jaimergp merged commit e5293c8 into main Jul 30, 2024
60 checks passed
@jaimergp jaimergp deleted the sunset-mambaforge branch July 30, 2024 12:01
jongyoul pushed a commit to apache/zeppelin that referenced this pull request Oct 1, 2024
### What is this PR for?

CI start failing at "Setup conda environment" because of

> October 2024: The Mambaforge installers will refuse to install during several pre-specified date ranges (i.e., ["brownouts"](https://en.wikipedia.org/wiki/Brownout_(software_engineering))) in order to encourage users to switch to Miniforge. These dates are
> - Every two weeks in October 2024 (2024-10-01, 2024-10-15)

https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/

The fix refers to conda-incubator/setup-miniconda#360

### What type of PR is it?

Bug Fix

### Todos

### What is the Jira issue?

ZEPPELIN-6117

### How should this be tested?

Pass GHA.

### Screenshots (if appropriate)

### Questions:
* Does the license files need to update? No.
* Is there breaking changes for older versions? No.
* Does this needs documentation? No.


Closes #4857 from pan3793/ZEPPELIN-6117.

Signed-off-by: Jongyoul Lee <[email protected]>
jongyoul pushed a commit to apache/zeppelin that referenced this pull request Oct 1, 2024
### What is this PR for?

CI start failing at "Setup conda environment" because of

> October 2024: The Mambaforge installers will refuse to install during several pre-specified date ranges (i.e., ["brownouts"](https://en.wikipedia.org/wiki/Brownout_(software_engineering))) in order to encourage users to switch to Miniforge. These dates are
> - Every two weeks in October 2024 (2024-10-01, 2024-10-15)

https://conda-forge.org/news/2024/07/29/sunsetting-mambaforge/

The fix refers to conda-incubator/setup-miniconda#360

### What type of PR is it?

Bug Fix

### Todos

### What is the Jira issue?

ZEPPELIN-6117

### How should this be tested?

Pass GHA.

### Screenshots (if appropriate)

### Questions:
* Does the license files need to update? No.
* Is there breaking changes for older versions? No.
* Does this needs documentation? No.

Closes #4857 from pan3793/ZEPPELIN-6117.

Signed-off-by: Jongyoul Lee <[email protected]>
(cherry picked from commit 383ae3b)
Signed-off-by: Jongyoul Lee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants