Add warnings to deprecate Mambaforge #615
Conversation
Miniforge3/mambaforge_deprecation.sh
Outdated
| echo "Future Miniforge releases will NOT build Mambaforge installers." | ||
| echo "We advise you switch to Miniforge at your earliest convenience." | ||
| echo "Sleeping for 30s..." | ||
| sleep 30 |
There was a problem hiding this comment.
We should probably make an announcement before we do this. When do it though, we should include the sleep for GHA as well.
There was a problem hiding this comment.
.github/workflows/ci.yml
Outdated
| run: | | ||
| echo "!!!!!! Mambaforge is now deprecated !!!!!" > MAMBAFORGE_LICENSE.txt | ||
| echo "Future Miniforge releases will NOT build Mambaforge installers." >> MAMBAFORGE_LICENSE.txt | ||
| echo "We advise you switch to Miniforge at your earliest convenience." >> MAMBAFORGE_LICENSE.txt |
There was a problem hiding this comment.
oh man, Miniforge vs Miniforge3..... naming decisions that come back to haunt us!!!!
There was a problem hiding this comment.
Yea... And how it's Miniforge3 for CPython but just Miniforge for PyPy :P
|
I added now some dates between October and end of the year where the installer will refuse to proceed:
Up for discussion, of course, but the setup is there now. |
|
Maybe we add the dates to the news item? |
|
OK I added them. |
Co-authored-by: Mark Harfouche <[email protected]>
|
The announcement is published so I think this is good to go. |
|
Is there a documented way of switching from mambaforge to miniforge? |
|
Is it already installed? If so. Nothing to be done. It’s fine. If it is in a ci pipeline, it’s so custom it’s hard for us to help. Just change “Mambaforge” to “Miniforge3” |
Comes from #602.
I've added:
To be decided, which deprecation periods we offer:
exit 1if the time and date is part of the preprogrammed brownout windowsIdeally we print this information in these scary messages already.