Release v1.2.0

[utam0k]

It's time we release the new patch version since we have met the milestone for v1.1.1 v1.2.0
https://github.com/opencontainers/runtime-spec/milestone/19

Previous release: #1213

Changes

Additions:

• config: add idmap and ridmap mount options (config: add idmap and ridmap mount options #1222)
• config.md: allow empty mappings for [r]idmap (config.md: allow empty mappings for [r]idmap #1224)
• features-linux: Expose idmap information ([Merged] features-linux: Expose idmap information #1219)
• mount: Allow relative mount destinations on Linux (mount: Allow relative mount destinations on Linux #1225)
• features: add potentiallyUnsafeConfigAnnotations (features: add potentiallyUnsafeConfigAnnotations #1205)
• config: add support for org.opencontainers.image annotations config: add support for org.opencontainers.image annotations #1197

Minor fixes:

• config: improve bind mount and propagation doc (config: improve bind mount and propagation doc #1228)

Documentation, CI & Governance:

• fix link to hooks in features (fix link to hooks in features #1226)
• specs-go: add missing deprecation comment for Hooks.Prestart (specs-go: add missing deprecation comment for Hooks.Prestart #1232)
• specs-go: mark LinuxMemory.Kernel as deprecated ()specs-go: mark LinuxMemory.Kernel as deprecated #1233)

---

[runtime-spec VOTE] tag 68346ed as v1.1.1 (at least 8 of 12 maintainers needed for this resolution to pass):

• @crosbymichael
• @mrunalp
• @vbatts
• @dqminh
• @tianon
• @hqhq
• @cyphar
• @giuseppe
• @AkihiroSuda
• @kolyshkin
• @thaJeztah
• @utam0k

[giuseppe]

LGTM

[AkihiroSuda]

ping @opencontainers/runtime-spec-maintainers

[thaJeztah]

Sorry, late to the party; I see various features being added; if we follow SemVer, should this increment the minor version, not the patch version? So v1.2.0 ?

[utam0k]

@thaJeztah Thanks for your comment. We haven't met the milestone for v1.2.0 yet.
https://github.com/opencontainers/runtime-spec/milestone/18

[thaJeztah]

We haven't met the milestone for v1.2.0 yet.
https://github.com/opencontainers/runtime-spec/milestone/18

Hm, right, but we passed changes for a patch release, as there's features in the diff.

SemVer is very clear on this; the version is baseed on the changes you're shipping, so you don't know the version "ahead of time". Is there a specific reason that milestone MUST be v1.2.0? Otherwise that milestone can become for v1.3.0.

I think there's 3 options;

1. if there's critical fixes merged that must be released; create a branch from the v1.1.0 tag, cherry-pick the fixes, and tag as v1.1.1
2. do a regular release; follow SemVer, which means: determine the version based on the changes; tag as v1.2.0, and move the linked milestone to "v1.3.0"
3. if there's a specific reason the next release MUST be v1.2.0; do a pre-release for ("v1.2.0-beta.1")

[AkihiroSuda]

do a regular release; follow SemVer, which means: determine the version based on the changes; tag as v1.2.0, and move the linked milestone to "v1.3.0"

👍

[kolyshkin]

LGTM

[AkihiroSuda]

@utam0k WDYT about renaming this to v1.2.0 ?

[utam0k]

I understand. I think it's good. I'll update it within a few days.

[utam0k]

@opencontainers/runtime-spec-maintainers I renamed this PR to v1.2.0. If you disagree, please cancel your vote. If you haven't done so already, please vote 🙏

[thaJeztah]

LGTM

[mrunalp]

@cyphar ptal.

[kolyshkin]

lgtm

[utam0k]

🚀 It's time to release v1.2.0