Skip to content
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

Separate versioning for refs and CAS portions of image-layout? #441

Closed
wking opened this issue Nov 3, 2016 · 4 comments
Closed

Separate versioning for refs and CAS portions of image-layout? #441

wking opened this issue Nov 3, 2016 · 4 comments

Comments

@wking
Copy link
Contributor

wking commented Nov 3, 2016

Spun off from #438, where I floated:

$ cat oci-layout
{
  "refsLayoutVersion": "1.0.0",
  "casLayoutVersion": "1.0.0"
}

The CAS and ref engines are completely orthogonal, and versioning them independently means that versions for a given component are bumped less frequently (e.g. a refs bump no longer triggers a CAS bump). That's less noise for implementers who are only focused on one or the other, but maybe the set of such implementers is empty?

@wking
Copy link
Contributor Author

wking commented Nov 3, 2016

There's also some discussion about the semantics of version-bumping oci-layout in #434 which is tangentially related to this.

@vbatts
Copy link
Member

vbatts commented Nov 3, 2016

IMO, this topic is distracting and adds to confusion.

@wking
Copy link
Contributor Author

wking commented Nov 3, 2016

On Thu, Nov 03, 2016 at 01:57:22PM -0700, Vincent Batts wrote:

IMO, this topic is distracting and adds to confusion.

You can close it wontfix if the argument doesn't hold water (e.g. “All
implementers will care about both, so it's not noise”).

Otherwise tag it priority/Pmaybe and forget about it until we hear
complaints (possibly never).

@stevvooe
Copy link
Contributor

I'm not sure I see the benefit of this.

Closing, per @vbatts.

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

No branches or pull requests

3 participants