Open kenodegard opened 4 months ago
Name | Link |
---|---|
Latest commit | 8813daa873d68e211a89c659be788e5d35c61f80 |
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...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@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!
Where should change requests be made? In the conda-build repo as an issue or as a CEP?
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 schema_version
is defined as an integer, incrementing the version anytime a new key is added seems very noisy
Built without sensitive environment variables
Name | Link |
---|---|
Latest commit | 50bf324c57de9c08bbb05050cbc79faca01c57c3 |
Latest deploy log | https://app.netlify.com/sites/conda-dot-org/deploys/66d8a856a3dbac0008ce7098 |
Deploy Preview | https://deploy-preview-190--conda-dot-org.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
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.