-
Notifications
You must be signed in to change notification settings - Fork 694
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
Comments
There's also some discussion about the semantics of version-bumping |
IMO, this topic is distracting and adds to confusion. |
On Thu, Nov 03, 2016 at 01:57:22PM -0700, Vincent Batts wrote:
You can close it wontfix if the argument doesn't hold water (e.g. “All Otherwise tag it priority/Pmaybe and forget about it until we hear |
I'm not sure I see the benefit of this. Closing, per @vbatts. |
Spun off from #438, where I floated:
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?
The text was updated successfully, but these errors were encountered: