-
Notifications
You must be signed in to change notification settings - Fork 554
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
Release v1.1.0 #1213
Release v1.1.0 #1213
Conversation
Through 07dd1f4 (2023-06-23) Signed-off-by: Akihiro Suda <[email protected]>
Very happy to see this! :) I propose to merge the release notes between the different rc's, and split off even-more-minor-than-minor changes into "Documentation, CI & Governance", see below the fold Merged release notesBreaking changes (but rather conforms to the existing runc implementation)
Deprecations
Additions
Minor fixes
Documentation, CI & Governance
|
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
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.
🚀 🚀 🚀
Thanks, @AkihiroSuda, for your coordination in releasing v1.1.0
I'm not sure about this. |
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 🧁
1.0.0 was a long time ago... I realize it's easier to just reflect what happened per rc, but now a reader needs to scroll over 30-40 almost irrelevant lines to get to the key content of the new version. Note that in a similar discussion for runc, Aleksa brought up https://keepachangelog.com as a reference, which says:
The proposed changelog is not human-friendly. |
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
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 (https://github.com/opencontainers/runtime-spec/compare/v1.0.2..ac7bb22)
I agree that a more human-friendly changelog would be nice, and if someone wanted to do the work to create one, we should probably integrate/use it, but the actual spec bits of the above comparison are relatively approachable (honestly, probably more approachable for implementers than the changelog/release notes would be anyhow).
I've made a proposal in the comment above, here again in plain-text for easy of use. It's based on appending the various iterations to rc1 (per section), and then splitting off "Documentation, CI & Governance" (because "Minor fixes" ended up being a giant heap, many of which weren't spec-relevant; obviously there are other subjective choices that could be made in grouping/ordering/etc.)
|
Co-Authored-By: H. Vetinari <[email protected]> Signed-off-by: Akihiro Suda <[email protected]>
Signed-off-by: Akihiro Suda <[email protected]>
Signed-off-by: Akihiro Suda <[email protected]>
bf5f6d3
to
3f552ce
Compare
Squashed the ChangeLog (Thanks to @h-vetinari) |
ping @opencontainers/runtime-spec-maintainers |
👋 Hi, @crosbymichael @dqminh @kolyshkin @mrunalp @thaJeztah |
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
Sounds like quorum has been reached. :) |
Let me merge the spec v1.1 PR and this blog PR simultaneously:
|
Changes (v1.1.0-rc.3 → v1.1.0)
Minor fixes and documentation:
Changes (v1.1.0-rc.2 → v1.1.0-rc.3)
Additions:
Minor fixes and documentation:
ociVersion
in example (chore: Update ociVersion in config-linux.md example #1199)s/features document/Features structure/g
(glossary: s/features document/Features structure/g #1203)Changes (v1.1.0-rc.1 → v1.1.0-rc.2)
Additions
features.md
to formalize therunc features
JSON (Addfeatures.md
to formalize therunc features
JSON #1130)Minor fixes and documentation
When serialized in JSON, the format MUST adhere to the following pattern
(runtime: removeWhen serialized in JSON, the format MUST adhere to the following pattern
#1178)Changes (v1.0.2 → v1.1.0-rc.1)
Breaking changes (but rather conforms to the existing runc implementation)
Deprecations
Additions
Minor fixes and documentation
LinuxSeccompFlag
s #1138)[runtime-spec VOTE] tag ac7bb22 as v1.1.0 (closes Mon Jul 3 06:02:25 AM UTC 2023)
(at least 8 of 12 maintainers needed for this resolution to pass):Closes #1052