Reiterating the importance of:
- Having more visibility and control over the list of feature flags that hidden behind the DCP flag as mentioned by @Klaussner
- Seamlessly integrate DCP with developer env without requiring the installation of AAP app or manual toggling on/off, as is the case with the current version as mentioned by @AdamAhmed
Additionally, it would greatly benefit us to include all new RFCs under the DCP umbrella, either by default or through their own set of feature flags, as we believe they are currently not included?
For example, we have DCP enabled on one of our testing environments for regression testing purposes, as well as on some other local instances across developers. However, none of these instances were able to capture the changes introduced by, for instance, RFC-33
Given the usual tight window for RFCs (~one month), we see lots of values of having them enabled by default on the development instances, while also allowing them to be toggled on/off individually and as needed.