Unfortunately, we do not. For the current batch of clean-up changes, it is certainly possible to add a kill switch. Time-consuming, certainly not nice (the kill switch will creep in in dozens of places in the code, if not hundreds), but possible.
For the upcoming set of rewrite-half-of-the-code changes, though, having a kill switch pretty much means forking the code of Session Restore into an "old" session restore and a new one. Do we have a policy on these things? Cheers, David On 5/22/13 5:16 AM, Ehsan Akhgari wrote: > Do we have a kill switch for the new stuff (a build-time flag or a > runtime pref) which we can use to turn this off on Beta if the add-on > compatibility problem proves to be bad enough that we would need to wait > for a while before we can ship this? I have experience maintaining a > branch to build and test Firefox with per-window private browsing turned > off at build-time which I used when Firefox 20 migrated through our > release channel and finally shipped. I would be happy to help you on > doing the same thing if needed. > > Cheers, > Ehsan > -- David Rajchenbach-Teller, PhD Performance Team, Mozilla _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
