Jump to content

Topic on Talk:Readers/Web/Team/Pushing production code from beta to stable

Optimise for allowing reverts

1
Phuedx (WMF) (talkcontribs)

This section should be stronger: all features, regardless of whether they are new or are replaceming existing ones, should be behind feature flags.

A natural consequence of this is that when replacing existing features, we have to keep old modules around until just after the proverbial switch has been flipped at the very least. It's up to the Tech Lead to schedule the tasks to tidy up the modules.

Reply to "Optimise for allowing reverts"