To-do: - define E10S_TESTING_ONLY to aurora - revert autostart=true to NIGHTLY only - tweak e10s opt-in popup text - discuss if a kill switch is necessary

Blassey, this is the current message that is displayed, up to 5 times if the user chooses "Not now" (There's also the "No thanks" option). I imagine we want to change the text for Aurora.. Any thoughts? And anything you want to tweak about the behavior?

I think dcamp had some ideas about the wording, NI'ing him

I'd suggest: a) Get rid of the e10s moniker - call it "Multi-process Firefox" or something. b) I'd be more urgent, and make it clear that this is becoming real soon. I'm no wordsmith, but I'd say something like: "Multi-process is coming soon to Firefox. You can start using it now to get early access to some of the benefits: * Improved responsiveness * Whatever other things Multi-process can be enabled from the preferences window. " Out of curiosity, how long does the "not now" nag delay?

We could also say something about addon compatibility - "If you're an addon developer, now's a great time to prepare your addon for Multi-Process Firefox" - but I'd worry about the nag getting too wordy.

Comment on attachment 8601576 [details] Current wording.png Let's update the wording as Dave suggested. Also NI'ing Matej to see if he has any edits

I've been going in circles about whether it should be "Less crashing" or "Fewer crashes," but I think I'm fine either way. Otherwise, looks good. Thanks.

Comment on attachment 8601489 [details] [diff] [review] E10S_TESTING_ONLY for Aurora Review of attachment 8601489 [details] [diff] [review]: ----------------------------------------------------------------- ::: configure.in @@ +3522,5 @@ > dnl ======================================================== > dnl Multiprocess Firefox Nightly Testing UI > dnl To be removed in Bug 1003313 > dnl ======================================================== > +if test -n "$NIGHTLY_BUILD" || test -n "$AURORA_BUILD"; then No need to add the AURORA_BUILD variable. You can just rely on RELEASE_BUILD not being set if you want something on aurora+nightly. (test -z "$RELEASE_BUILD")

Comment on attachment 8601828 [details] [diff] [review] E10S_TESTING_ONLY for Aurora Review of attachment 8601828 [details] [diff] [review]: ----------------------------------------------------------------- ::: configure.in @@ +3519,5 @@ > AC_SUBST(RELEASE_BUILD) > > dnl ======================================================== > dnl Multiprocess Firefox Nightly Testing UI > dnl To be removed in Bug 1003313 You may want to update this comment to say this is enabled on aurora and nightly.

So taking from everyone's comments, I'll go with the following text if I don't hear objections: " Multi-process is coming soon to Firefox. You can start using it now to get early access to some of the benefits: * Improved responsiveness * Fewer crashes " I tried including the message to add-on developers but the popup felt too heavy, and it's something that non add-on developers users don't need to read, so I removed it.

Blassey, one last question: all of the strings related to e10s experimentation are currently hardcoded because non-english strings didn't have much value in Nightly and we didn't want to bother localizers with strings that will not make it to release. This trade-off might be different for Aurora though. Do you want to keep them English only (and perhaps only display the popup to english users), or make them localizable? Talking about this with Mossop we figured we could make them localizable and add a Localization Note saying that won't ride the trains, so that the contributors can decide for themselves if it's worth spending their time on that or not.

Since we're at least considering prompting for beta as well, let's go ahead and make them localizable and add a note saying this won't hit beta until at least 41

I've tested on Windows 7 64bit, Ubuntu 12.04 and Mac OSX 10.9.5 using latest Aurora 41.0a2 (buildID: 20150712004007) and I have the following results: - on Windows and Mac: when I opened Firefox with a clean profile, the e10s pop-up is displayed for 1 second and then disappears (and also disappears the notification icon from Navigation Bar) -> I restarted Firefox and the notification icon is correctly displayed now under Navigation Bar. - on Ubuntu: the same behaviour, but here, after restart, the notification icon is not displayed anymore. Any thoughts about that?

I only reviewed build changes, I have no idea.

Since we've enabled e10s by default in DevEdition 42, it seems like there's nothing more to do here.

(In reply to Camelia Badau, QA [:cbadau] from comment #18) > I've tested on Windows 7 64bit, Ubuntu 12.04 and Mac OSX 10.9.5 using latest > Aurora 41.0a2 (buildID: 20150712004007) and I have the following results: > > - on Windows and Mac: when I opened Firefox with a clean profile, the e10s > pop-up is displayed for 1 second and then disappears (and also disappears > the notification icon from Navigation Bar) -> I restarted Firefox and the > notification icon is correctly displayed now under Navigation Bar. > - on Ubuntu: the same behaviour, but here, after restart, the notification > icon is not displayed anymore. > > Any thoughts about that? I think this was caused by the "Make FF your default browser" alert, which would only hope for brand new profiles. And since in Aurora starting from 42 we've enabled e10s by default too, I believe we don't need to worry about this.