This discussion aims to explore the challenge of backwards compatibility in JavaScript and PHP APIs from the Gutenberg project into WordPress core. Currently, there is little clarity around maintenance of backward compatibility across the project, resulting in confusion for developers and performance issues. There are two focus areas:
- Depreciating officially stable APIs that have been replaced
- Depreciating unstable, experimental, or internal APIs that have been shipped in WordPress.
Perspectives needed: Senior WordPress Core contributors/committers with deep knowledge of past lessons learned around backwards compatibility, Gutenberg contributors with working knowledge around processes and decision making.
Facilitator: Marius Jensen