Skip to content

Conversation

@ashokponkumar
Copy link

Signed-off-by: Ashok Pon Kumar ashokponkumar@gmail.com

Signed-off-by: Ashok Pon Kumar <ashokponkumar@gmail.com>
@thaJeztah
Copy link
Member

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)

@thaJeztah
Copy link
Member

did a quick write-up; #1069

@mikebrow
Copy link
Member

mikebrow commented Oct 2, 2020

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)

@vbatts
Copy link
Member

vbatts commented Apr 20, 2022

closing in favor of getting a release tagging process in place

@vbatts vbatts closed this Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants