Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a backward compatibility document #18499
Among team members and WordPress developers, there's a lot of assumptions on backward compatibility and knowledge that is not shared properly to all contributors.
While this first document is probably unperfect, it is at least a good starting point to understand the backward compatibility policy in Gutenberg and WordPress.
nerrad left a comment
I do have some concerns that we're setting up false expectations by using the term guarantee though. While I appreciate it grants additional significance to how backwards-compatibility is viewed, WP itself doesn't explicitly guarantee backwards compatibility anywhere (that I know of). So my suggestions are mostly around softening the language a bit.
Awesome work on this document. I’m really happy to see all that clarified and now easy to share during the code review.
I’m happy about the part which states that class names aren’t part of the public API. I assumed they are based on the fact that theme authors use them extensively.