-
Notifications
You must be signed in to change notification settings - Fork 35
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
Conversation
✅ Deploy Preview for conda-dot-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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
@wolfv I'd greatly appreciate your input here |
I generally like it a lot. Parts of it are a bit over the top and chat-botty (ie. paramount) and parts are a bit unspecific (e.g. what is the process exactly that you want to follow? Where should change requests be made? In the conda-build repo as an issue or as a CEP?). But I think more communication is better so I would happy to see a blog post like this asap! :) |
PS sorry for taking so long to add my input! |
Honestly this is where I was waiting for the steering council to tell me what they expected. For any updates to the new recipe format what do we expect to happen? I'm under the assumption it will require a CEP and a recipe version bump. Or are these recipe format changes batched and only released as a new version after some time? Or is the recipe version only bumped if an existing key is modified/removed (i.e., adding new keys doesn't result in a bump)? |
Since the |
✅ Deploy Preview for conda-dot-org ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
blog/news.json
Outdated
], | ||
"description": "The recent approval of the new recipe format (`recipe.yaml`, v1) does not mean the end of the old format (`meta.yaml`, v0). The conda community must balance innovation with support for legacy systems.\n", | ||
"image": "img/blog/2024-09-04-v0-format-modifications/banner.png", | ||
"date": "2024-05-20T00:00:00" |
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.
The date here needs to be updated
@@ -1,60 +1,62 @@ | |||
--- |
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.
This file should be renamed to reflect the new publication date (vs 2024-05-20
)
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
@kenodegard - is this good to go? |
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.
Some tiny punctuation suggestions
Co-authored-by: Katherine Kinnaman <[email protected]>
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.
LGTM!
I have two minor comments:
Otherwise nice blog post! |
Co-authored-by: jaimergp <[email protected]>
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.