Experimental Features
All Symfony features benefit from ourBackward Compatibility Promise to give developers the confidence to upgrade to newversions safely and more often.
But sometimes, a new feature is controversial or you cannot find a convincing API.In such cases, we prefer to gather feedback from real-world usage, adaptthe API, or remove it altogether. Doing so is not possible with a no BC-breakapproach.
To avoid being bound to our backward compatibility promise, such features canbe marked asexperimental and their classes and methods must be marked withthe@experimental tag.
A feature can be marked as being experimental for only one minor version, andcan never be introduced in anLTS version. The core teamcan decide to extend the experimental period for another minor version on acase by case basis.
To ease upgrading projects using experimental features, the changelog mustexplain backward incompatible changes and explain how to upgrade code.
