-
Notifications
You must be signed in to change notification settings - Fork 33
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 blogpost about v0 recipe changes #190
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for conda-dot-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
2. Approval: The proposed modification should undergo the same review and | ||
approval expected for the v1 format. |
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.
is a CEP required for all modifications to the v1 format?
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 wonder too. We are going to need modifications to the menuinst CEP too after some work that @marcoesters did, so I was kind of wishing we would have a fast-track for smaller additions and corrections, but AFAIK we don't have such a process (yet?).
As the community navigates the transition from v0 to v1, clear communication and | ||
guidance are paramount. Developers and maintainers need to be equipped with the | ||
resources and support necessary to understand the implications of the new format | ||
and make informed decisions about when and how to migrate. Additionally, robust | ||
documentation and educational materials will play a crucial role in facilitating | ||
this transition seamlessly. |
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.
Should we include a link to https://prefix-dev.github.io/rattler-build/latest/recipe_file/? Or is there some other migration doc that is better suited?
Should we mention https://github.com/conda-incubator/conda-recipe-manager?
Co-authored-by: jaimergp <[email protected]>
for more information, see https://pre-commit.ci
Co-authored-by: Bianca Henderson <[email protected]>
5d032e8
to
8813daa
Compare
The approval of the v1 format represents an exciting step forward for the conda | ||
ecosystem. However, it's essential to recognize that change takes time, and the | ||
transition to the new format will be gradual. In the interim, the v0 format |
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.
Might be worth mentioning https://github.com/conda-incubator/conda-recipe-manager as a way to simplify the 80% of cases?
@wolfv I'd greatly appreciate your input here |
Description
This adds a blog post discussing when and how to go about making changes to the v0 recipe format now that v1 has been approved and is being prototyped in rattler-build.