-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
Enumerate version maintenance and version bumps #82
Comments
The new index format should fully backwards compatible, since it doesn't touch any existing URLs, and is made available via entirely new URLs. FWIW, we have reached release candidate for Bundler 1.12, which has support for the new index. We've also shipped the new index in |
Agreement then @smellsblue ? |
I think we should spell out in the documentation:
I would like to follow semantic versioning, though to do so we should figure out what our API is, so we know when we are making a backwards incompatible change.
If we do so, then the biggest thing on my mind... is the new index format a backwards incompatible change or not? I think we could reasonably say that any HTTP requests happening behind the scenes are not really our API, and so I would consider it a minor update. Yet, it is still potentially a big change that introduces risk, and that might not be conveyed properly in a minor version update, so maybe that doesn't matter.
/cc @pcarranza @indirect
The text was updated successfully, but these errors were encountered: