Add blog post to summarize upcoming spec changes #130
Conversation
Signed-off-by: Josh Dolitsky <[email protected]>
… into 2023-07-07-summary-of-upcoming-changes
...sts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1.md
Outdated
Show resolved
Hide resolved
...sts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1.md
Outdated
Show resolved
Hide resolved
...sts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1.md
Outdated
Show resolved
Hide resolved
...sts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1.md
Outdated
Show resolved
Hide resolved
|
Other things I can think of to add:
|
fix typos found by tianon in review Co-authored-by: Tianon Gravi <[email protected]> Signed-off-by: Josh Dolitsky <[email protected]>
|
@sudo-bmitch - in the final section "Closing Thoughts" I mention that this is just the major stuff. How do you feel about just adding your list as bullets at the end, but not going into detail? |
|
Oh I was just keeping it to the big stuff, and I'm not even sure how to word that registries cannot implement an allow list of artifacts in this, which also feels big to me. Or the change in the regexp for the repository value. But keeping the description to a short bulleted list works. |
Signed-off-by: Josh Dolitsky <[email protected]>
…dolitsky/opencontainers.org into 2023-07-07-summary-of-upcoming-changes
|
@sudo-bmitch @tianon - just added some updates to address your feedback, please lmk how that looks |
...sts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1.md
Show resolved
Hide resolved
Signed-off-by: Josh Dolitsky <[email protected]>
| The version of the upcoming minor releases of both OCI Image and | ||
| Distribution spec happens to be the same: `v1.1.0`. |
There was a problem hiding this comment.
It seems opencontainers-specs are self-aligning, as the runtime spec is also looking to release 1.1.0 any moment now...
There was a problem hiding this comment.
yes, but not intentional 😅 may not always be the case in the future
No description provided.