Not sure how we can accomplish this. I'm wondering if rel-eng can flip some sort of switch? If not, maybe we can land a patch on elm that would transition people to mc over a period of time.

We may want to make announcements about m-c then audit the number of remaining daily active users on elm to see if this is worth doing or not.

I think if we decide to do this we have to get nthomas to construct a custom MAR that would do it. I know they always have a ton of things to do though so that's why I suggested we evaluate whether it's worth it or not.

We have about 2,800 nightly users on elm.

(In reply to Brian R. Bondy [:bbondy] from comment #1) > We may want to make announcements about m-c then audit the number of > remaining daily active users on elm to see if this is worth doing or not. Yeah if we can get them to move off voluntarily over a couple weeks, that would make our job much simpler.

We had some success in bug 819857 with doing this kind of thing. The basic idea is to modify the elm repo to hardcode the update channel in the mozconfigs to 'nightly', and allow the channel-prefs.js file to be included in the mar file (see bug 819857 comment #3). The flow for users is then * update on nightly-elm to first build with above changes * update requests are on nightly from them on, first update moves them to an m-c nightly We know this works fine from a mar signing point of view. Unfortunately the changeset we used for birch is long gone so you'll need to reconstruct it.

We can start by posting the specifics of the move to newsgroups tomorrow to get the ball rolling. If we can't get folks to move over on their own after a couple weeks, we can start hacking on elm per comment 5.

Asa's blog post and related press don't seem to be helping. 2,879 souls still on elm.

Current # is 2,529

(In reply to Nick Thomas [:nthomas] from comment #5) > We had some success in bug 819857 with doing this kind of thing. The basic > idea is to modify the elm repo to hardcode the update channel in the > mozconfigs to 'nightly', and allow the channel-prefs.js file to be included > in the mar file (see bug 819857 comment #3). > > The flow for users is then > * update on nightly-elm to first build with above changes > * update requests are on nightly from them on, first update moves them to an > m-c nightly > > We know this works fine from a mar signing point of view. Unfortunately the > changeset we used for birch is long gone so you'll need to reconstruct it. What precisely does engineering need to provide to RelEng to make this happen ASAP? We very much and very quickly need those users moved to m-c.

Hi nthomas, Please see Comment 9. Is there a way you or someone else could do this for us on the RelEng side? Is there any extra info you need from us to help make it happen?

I landed the change to do this at https://tbpl.mozilla.org/?tree=Elm&rev=da31724af637 and will verify in the dep build that it worked as expected. I've only done Windows since that's where the vast majority of the users are. Some nightlies will happen automagically. After updating to that the build will look for updates on nightly (aka mozilla-central). Note there are no updates on nightly until bug 852106 is resolved.

(In reply to Nick Thomas [:nthomas] from comment #11) > I landed the change to do this at > https://tbpl.mozilla.org/?tree=Elm&rev=da31724af637 > and will verify in the dep build that it worked as expected. Done: AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/21.0a1/20130318203314/WINNT_x86-msvc/en-US/nightly/Windows_NT%205.1.3.0%20(x86)/default/default/update.xml?force=1 ie nightly not nightly-elm

Win32 nightly got interrupted by a network glitch, rerunning it.

The nightly build finished but there's a bug in the code that publishes the update information, so that new build isn't being offered yet. I'll correct that on Wednesday (PDT).

Thanks for getting to this so quickly nthommas

Last nightly before this work: http://hg.mozilla.org/projects/elm/rev/88c6f1ab7371 AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/21.0a1/20130213040206/WINNT_x86-msvc/en-US/nightly-elm/Windows_NT%205.1.3.0%20(x86)/default/default/update.xml?force=1 Apply update and then: http://hg.mozilla.org/projects/elm/rev/da31724af637a AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/21.0a1/20130319040203/WINNT_x86-msvc/en-US/nightly/Windows_NT%205.1.3.0%20(x86)/default/default/update.xml?force=1 Apply update and then: http://hg.mozilla.org/mozilla-central/rev/8156df33b757 AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/22.0a1/20130320031103/WINNT_x86-msvc/en-US/nightly/Windows_NT%205.1.3.0%20(x86)/default/default/update.xml?force=1 (no update found) And diffing against an m-c install is clean, so I've left this enabled. Please monitor for the ADI dropping. [Releng: Added elm to the list of directories which are ignored when cleaning up nightly snippets, ffxbld cron on aus3-staging]

Please reopen if there are any issues.

We got a nice drop yesterday - from 2.5K to 2.2K. Will keep an eye on it.

Down to 990.

Awesome! Thanks Nick.

We're down to about 100 elm users with version 21.0, plus another 375 or so on older versions. The latter group are declining slowly are likely to be people with technical or philosophical reasons for not taking updates.

Asa can I give the elm branch back?

(In reply to Brian R. Bondy [:bbondy] from comment #22) > Asa can I give the elm branch back? Yes. I think we've done what we can here.