-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Remove now outdated paragraphs from Versions section #3219
Remove now outdated paragraphs from Versions section #3219
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we wan to remove this entirely, or explain the exception for OAS 3.0 to OAS 3.1. Either way, I agree it needs to change, and this change would work for me.
I'm against this change. The 3.0 series of releases has their rules / had them at the time of writing. |
The well-intended 3.0 rules clearly have joined the dinosaurs now, and retaining them in a document published after their demise is really confusing. |
@MikeRalphson what about instead adding a note that this policy was changed in 3.1.0 and referring readers to that document for further details? That would leave the policy as defined in place, but correctly set expectations that it has not been followed exactly. |
It feels odd to me that a 3.0.x document 'knows about' a 3.1.x document, even if it post-dates it. I think that's my gut objection. |
I think the important thing here is the UX more than forward knowledge. The current text sets an incorrect expectation which is very bad UX. |
Closed in favor of #3214 after discussion in TDC |
Fixes #3195
Alternative to #3214