Hello edx-code, *Feature Toggle Best Practices*
We use feature toggles extensively in our system to selectively enable a feature for certain users or certain deployments and more generally to decouple deployment of code from release (enablement) of the code. When used with care, feature toggles can be a powerful tool that enable many use cases. However, feature toggles inherently add complexity to the code since they introduce multiple paths and configuration operations. Let's align on a common best practice for feature toggling as it is critical for both the short-term and long-term health of the open edX system. Please refer to the PR for feature toggle best practices <https://github.com/edx/open-edx-proposals/pull/54>. *Review Feedback* You may share your comments/feedback by (in order of preference): - posting on the PR <https://github.com/edx/open-edx-proposals/pull/54>. - starting a thread on #architecture on slack <https://openedx.slack.com/messages/C0RU5BTCP/details/>, which we would eventually record in the OEP PR. - contacting me or Eric <efisc...@edx.org> (the Arbiter of this OEP), with the intent of capturing a summary of the conversation on the PR. *Timeline* As specified in the PR, the target review end date is *March 7th*. If needed, we will extend the deadline. Thanks, Nimisha (and Eric as "Arbiter") -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CACSOLjc_A0P2p%3DTcNJ7vAu2kGCjYVM9Bm5kStudeAU6Sys3ODA%40mail.gmail.com.
