Hi all, Please provide any final comments/feedback/etc on this OEP by EOD today. Unless there are any blocking issues, we plan to merge it as "Accepted" tomorrow.
Thanks, Nimisha (and Eric as "Arbiter") On Wed, Feb 28, 2018 at 2:32 PM, Nimisha Asthagiri <[email protected]> wrote: > 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 <[email protected]> (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 19th **(extended > from March 7th).* > > 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/CACSOLjdm%2BUp2peuzepv%3DWXGKaFTOejgnna8rW%2Bgi_ohEect0-Q%40mail.gmail.com.
