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

Add blogpost about v0 recipe changes #190

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

kenodegard
Copy link
Contributor

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.

Copy link

netlify bot commented May 8, 2024

Deploy Preview for conda-dot-org ready!

Name Link
🔨 Latest commit 8813daa
🔍 Latest deploy log https://app.netlify.com/sites/conda-dot-org/deploys/664b96732c86c20007de5f43
😎 Deploy Preview https://deploy-preview-190--conda-dot-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Comment on lines 48 to 49
2. Approval: The proposed modification should undergo the same review and
approval expected for the v1 format.
Copy link
Contributor Author

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?

Copy link
Member

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?).

blog/2024-05-08-v0-format-modifications.mdx Outdated Show resolved Hide resolved
Comment on lines 46 to 51
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.
Copy link
Contributor Author

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?

Comment on lines +54 to +56
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
Copy link
Member

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?

@kenodegard kenodegard marked this pull request as ready for review June 11, 2024 16:03
@kenodegard kenodegard requested a review from wolfv June 11, 2024 16:04
@kenodegard
Copy link
Contributor Author

@wolfv I'd greatly appreciate your input here

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.

None yet

4 participants