"All schema changes must be optional for your code"?
Regarding this change, is it no longer the case that we can submit the schema change in one patch and the code change in a followup, and -2 the latter with a comment "Don't merge this until the schema change is made to WMF wikis", rather than contributing to the proliferation of nearly-useless feature flags? The case I'm considering here is the one I've most often encountered: a new feature requires a new index (or an old index that was never deployed) or else the query is very slow, but other than for disabling the feature until the index is deployed a feature flag would be utterly pointless. Anomie (talk) 14:44, 4 February 2014 (UTC)
- That is probably fine, honestly. I'm parroting the Dev Policy page and I feel weird just unilaterally changing that, could you? :) I just don't want more changes to go through that don't take the WMF cluster into account. Greg Grossmeier (talk) 15:58, 4 February 2014 (UTC)