-
Notifications
You must be signed in to change notification settings - Fork 59
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
Provide Guidelines on version handling of endpoints across the eiffel-community #232
Comments
I agree it would be good to have a common guideline on how REST APIs in general and version handling in REST APIs in specifically should work across tools in the Eiffel eco-system. |
This issue does actually not belong in the Eiffel protocol repo, as it is about eco-system tools and not about the protocol. Should it be added to the Community repo maybe https://github.com/eiffel-community/community? Or do you think we'd need a new repo to keep common Eiffel Eco System documents/sources? |
I agree, I will write it in the community instead and will close this. |
Created an issue in community eiffel-community/community#35 and closing this one. |
Description
There is no common guidelines about how to support the version handling and how long we should support the deprecated endpoints. This issue is create to make a guidelines available across the community so that we adhere the same across different repositories
Motivation
We have different repositories adhering to different ways w.r.t version handling of endpoints, so this can be brought in as a common way to support them.
Exemplification
Benefits
Possible Drawbacks
The text was updated successfully, but these errors were encountered: