Jannis Leidel

> I have several concerns with this PR: > > * I'm not sure I would consider `@EXPLICIT` a different format than `requirements.txt`, so I'm not sure I would have...

I want to do a light refactor as suggested by you and Jonathan, and base it on top of #14870, I think that'll be a good step in between, I'll...

That would be more compatible, and users wouldn't be impacted by it. I think I like that idea, @kenodegard

pre-commit.ci autofix

pre-commit.ci autofix

> Are we sure we really want to deprecate the cran skeleton already? > > * This afaik is still true: [[WIP]cran support grayskull#423 (comment)](https://github.com/conda/grayskull/pull/423#issuecomment-1403798517) > * The existing cran...

I think we failed at long-running branches in the past and it became a burden (maybe resource related), but you're right, it might also work as an alternative. I do...

Okay, thinking this through some more, I think compared to the existing deprecations framework we have two different constraints here: - we primarily want to keep ourselves honest about adding...

I don't know what's the next move here, I've asked for feedback in https://github.com/conda/conda/pull/14928#issuecomment-3199544059. I think I've heard a few people say they don't like the proposal.

> What do we need to do in order to make `conda remove` and `conda env remove` look and act the same? I.e. same arguments and same default behavior? -...