Experimental

[OskarStark]

We should introduce alle these packages and bundles as experimental. That means we would need to mark dedicated classes with @experimental and mention it in the docs, README and CHANGELOG

WDYT @fabpot ?

[fabpot]

It makes a ton of sense. Let's do it like we're doing for Symfony components.

[chr-hertel]

Yes please, sounds good

[chr-hertel]

Added the disclaimer

This Bundle is experimental. Experimental features are not covered by Symfony's Backward Compatibility Promise.

in all README files of components and bundles. Is that sufficient?

[OskarStark]

Yes, but more important is to add the @experimental annotation to the classes we want to be able to change later without a bc break

[wouterj]

It's pretty early, but note that this would automatically mean this will be a 8.0 feature as we don't allow experimental code in LTS releases. But that suits perfectly: it's a great headline for the new major and it gives us the most experimental time before the next LTS.

[fabpot]

As the ecosystem still evolves super fast, I’m not sure we will reintegrate it in the Symfony mono repo so fast. It will probably need releases more often.