What does it mean for a feature to be "experimental" in Zebra?

[mpguerra]

As we start to prototype and try out new features for zebra we've started accumulating a number of experimental features that we've been asking people to try out and provide feedback on.

How should we set expectations about how these experimental features should be used and the types and levels of support we can provide users of these features?

For example, ECC has used the following wording in the past:

This is an experimental feature so there are no guarantees that the protocol, database format, RPC interface etc. will
remain the same in the future.

and

Experimental Features provide new functionality which has received the standard review and testing of other zcashd features. However, they typically have not had widespread use in production and their behavior or interface may change between releases. We do not recommend using them in large scale production environments.

We should think about what the criteria are for a feature to be deemed experimental in Zebra and formulate similar wording to set the right expectations