-
Notifications
You must be signed in to change notification settings - Fork 144
[DOCS] Add an API and deprecation policy #720
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
Conversation
As discussed here: #715
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.
Just some typos in one sentence.
It occurs to me that we ourselves need to track when we mark something as @internal
to ensure we don't make make any breaking changes before the next major release since doing so. I don't know if we can use something like "@internal
may be changed or removed without notice from version 9.0.0" in the PHPDoc. This doesn't affect this PR, I'm just concerned that we might for example start making breaking changes to a class marked as @internal
for 8.7 for a bugfix which is then included in 8.7.1, not realizing (or forgetting) it had not been marked @internal
in 8.6.
Co-authored-by: JakeQZ <jake@qzdesign.co.uk>
This is exactly the same change as in our sister project, PHP-CSS-Parser: MyIntervals/PHP-CSS-Parser#720
This is exactly the same change as in our sister project, PHP-CSS-Parser: MyIntervals/PHP-CSS-Parser#720
This is exactly the same change as in our sister project, PHP-CSS-Parser: MyIntervals/PHP-CSS-Parser#720
This is exactly the same change as in our sister project, PHP-CSS-Parser: MyIntervals/PHP-CSS-Parser#720
As discussed here:
#715