oh! reminds me I wanted to write a proposal to consider tagging the go implementation separate from the main repository. Doing so would allow doing intermediate releases of the go implementation (fixes in Go that don't affect the runtime spec itself).

If that would be accepted as proposal, I think the go.mod should be inside the spec-go directory (basically becoming a submodule with its own tag)

did a quick write-up; #1069

oh! reminds me I wanted to write a proposal to consider tagging the go implementation separate from the main repository. Doing so would allow doing intermediate releases of the go implementation (fixes in Go that don't affect the runtime spec itself).

If that would be accepted as proposal, I think the go.mod should be inside the spec-go directory (basically becoming a submodule with its own tag)

Nice.. I was simultaneously thinking pretty much the same thing over here: opencontainers/distribution-spec#192 (review)

closing in favor of getting a release tagging process in place