1159996 - Please deploy 0.16.0 loop-client to PRODUCTION

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Richard Pappalardo [:rpapa][:rpappalardo]]

------------------
RELEASE NOTES
------------------
https://github.com/mozilla/loop-client/releases

COMPARISONS
https://github.com/mozilla/loop-client/compare/0.13.5...0.14.0
https://github.com/mozilla/loop-client/compare/0.14.0...0.15.0
https://github.com/mozilla/loop-client/compare/0.15.0...0.16.0

TAGS
https://github.com/mozilla/loop-client/releases/tag/0.16.0
https://github.com/mozilla/loop-client/commit/99108a80bca899ccc33f2231e8c8b5c58fa4a83f

CHANGELOG
0.16.0 (2015-04-28)
-------------------

- Bug 1141128 - add a margin of 10px to the left side of the remote video stream in the Loop standalone client
- Bug 1141133 - Implement encrypt/decrypt of context information ready for Loop's context in conversation work
- Bug 1137843 - Loop client should not try to leave room that it fails to join
- Bug 1146929 - Remove support for the old style call hash based urls from the Loop standalone UI
- Bug 1114563 - Show the room name before the user enters the room
- Bug 1132301 - Part 3 - hide the Loop dropdowns when the content window loses focus, so mouseLeave workarounds can be removed
- Bug 1105490 - Remove old ToS generation code from Loop Standalone
- Bug 1147609 - Make Loop's standalone UI work with roomName as an unencrypted parameter or as an encrypted part of context
- Bug 1146834 - use Uint8Array's subarray when slice is not available in Loop content pages
- Bug 1150273 - Use eslint for the react files for Loop
- Bug 1152296 - Move roomStore.js from shared code to desktop specific code for Loop
- Bug 1136797 - For Loop standalone rename the brand website url to download firefox url and update the default
- Bug 1132301 - Part 3 hide the Loop dropdowns when the content window loses focus, so mouseLeave workarounds can be removed
- Bug 1142522 - Part 1 Share utils and crypto content modules with chrome as well
- Bug 1142522 - Part 2 Hook up encryption for room contexts in guest mode
- Bug 1153418 - Fix an issue on Loop's standalone where the remote and video alignment during screenshare is 10px out
- Bug 1142588 - Implement context in conversations display for Loop's standalone UI
- Bug 1155036 - Standalone display is unusable at 640x500
- Bug 1154862 - Add forgotten param to VideoDimensionsChanged action
- Bug 1154868 - Log exceptions in bufferedUpdateVideo callbacks
- Bug 1155561 - ignore body clicks on dropdown menu buttons, to make dropdowns in Loop windows toggle properly
- Bug 1079697 - Remove obsolete jshint messages in Loop code
- Bug 1132222 - Add more metrics reporting to the Loop standalone UI
- Bug 1156201 - Reset the video dimensions cache when in initial room states to avoid issues with not correctly displaying video streams when a room is re-entered
- Bug 1137813 - Add room connection status logging
- Bug 1158800 - Don't show errors for context in conversations on the standalone UI as they may force the user into an unnecessary re-obtaining of the URL
- Update L10n to latest versions

Config changes:
- Added loop.config.downloadFirefoxUrl
- Removed loop.config.brandWebsiteUrl

Comment 1

[Richard Pappalardo [:rpapa][:rpappalardo]]

Bob has deployed prod stack ELB

------------------
SUMMARY (PRE-DNS-SWITCH ELB)
------------------

Placed several calls successfully between Nightly and DevEd (Aurora) using new loop-client 0.16.0 ELB.


tab and window sharing works with DevEd, but only window sharing works with Nightly.
This is a known issue, per :Standard8 - bug 1137634 - its e10s only and doesn't affect release users at the moment...

Privacy & ToS links - OK.

Verifying ELB stack.  


------------------
VERIFICATION (PRE-DNS-SWITCH ELB)
------------------

Can no longer verify deployed version number so identifying correct release by features in this build.

NOTE:
We need to get some instance verification mechanism restored!


$ curl -I https://hello.firefox.com
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 7233
Content-Security-Policy: frame-ancestors 'self'
Content-Type: text/html
Date: Thu, 30 Apr 2015 21:33:27 GMT
ETag: "553f6072-1c41"
Last-Modified: Tue, 28 Apr 2015 10:26:58 GMT
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
X-Token-Match: 1
Connection: keep-alive


https://hello.firefox.com/config.js:
var loop = loop || {};

loop.config = {
  serverUrl: 'https://loop.services.mozilla.com/v0',
  feedbackApiUrl: 'https://input.mozilla.org/api/v1/feedback',
  feedbackProductName: 'Loop',
  downloadFirefoxUrl: 'https://www.mozilla.org/firefox/new/?scene=2&utm_source=hello.firefox.com&utm_medium=referral&utm_campaign=non-webrtc-browser\#download-fx',
  privacyWebsiteUrl: 'https://www.mozilla.org/privacy/firefox-hello/',
  legalWebsiteUrl: 'https://www.mozilla.org/about/legal/terms/firefox-hello/',
  marketplaceUrl: 'https://marketplace.firefox.com/iframe-install.html',
  learnMoreUrl: 'https://www.mozilla.org/hello/',
  roomsSupportUrl: 'https://support.mozilla.org/kb/group-conversations-firefox-hello-webrtc',
  guestSupportUrl: 'https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode',
  generalSupportUrl: 'https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode',
  unsupportedPlatformUrl: 'https://support.mozilla.org/kb/which-browsers-will-work-firefox-hello-video-chat',
  fxosApp: {
    name: 'Firefox Hello',
    manifestUrl: 'https://marketplace.firefox.com/app/54b83aea-1208-4605-82eb-22819f39d81d/manifest.webapp',
    rooms: true
  }
};



PRIVACY & ToS LINKS - OK!

https://loop.services.mozilla.com
{"name":"mozilla-loop-server","description":"The Mozilla Loop (WebRTC App) server","version":"0.17.7","homepage":"https://github.com/mozilla-services/loop-server/","endpoint":"https://loop.services.mozilla.com","fakeTokBox":false,"fxaOAuth":true,"i18n":{"defaultLang":"en-US","lang":"en-US"}}

Comment 2

[Bob Micheletto [:bobm]]

Deployment complete.  Closing this bug.

Comment 3

[Richard Pappalardo [:rpapa][:rpappalardo]]

------------------
SUMMARY 
------------------

tab and window sharing works with Nightly, DevEd, with exception of known tab-sharing issue with e10s on Nightly. 

Placed several calls successfully between Nightly and DevEd (Aurora) using loop-client 0.16.0 (after DNS switch).
Also placed calls to pdehaan, bobm & whd.  I couldn't hear audio from bobm & whd, but they had no issues when calling one another.  

Mark, do you know if there are bug(s) for tracking problems related to video/audio not transmitting?  About half the loop calls I make seem to have this kind of issue.  It seems to be when calling specific users and unrelated to any particular deployment.  Not sure if device/network related or what's being done if anything to gather telemetry on this.

------------------
VERIFICATION
------------------

Can no longer verify deployed version number so identifying correct release by features in this build.

NOTE:
We need to get some instance verification mechanism restored!

$ curl -I https://hello.firefox.com
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 7233
Content-Security-Policy: frame-ancestors 'self'
Content-Type: text/html
Date: Fri, 01 May 2015 03:27:45 GMT
ETag: "553f6072-1c41"
Last-Modified: Tue, 28 Apr 2015 10:26:58 GMT
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
X-Token-Match: 1
Connection: keep-alive



https://hello.firefox.com/config.js:
var loop = loop || {}; loop.config = { serverUrl: 'https://loop.services.mozilla.com/v0', feedbackApiUrl: 'https://input.mozilla.org/api/v1/feedback', feedbackProductName: 'Loop', downloadFirefoxUrl: 'https://www.mozilla.org/firefox/new/?scene=2&utm_source=hello.firefox.com&utm_medium=referral&utm_campaign=non-webrtc-browser\#download-fx', privacyWebsiteUrl: 'https://www.mozilla.org/privacy/firefox-hello/', legalWebsiteUrl: 'https://www.mozilla.org/about/legal/terms/firefox-hello/', marketplaceUrl: 'https://marketplace.firefox.com/iframe-install.html', learnMoreUrl: 'https://www.mozilla.org/hello/', roomsSupportUrl: 'https://support.mozilla.org/kb/group-conversations-firefox-hello-webrtc', guestSupportUrl: 'https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode', generalSupportUrl: 'https://support.mozilla.org/kb/respond-firefox-hello-invitation-guest-mode', unsupportedPlatformUrl: 'https://support.mozilla.org/kb/which-browsers-will-work-firefox-hello-video-chat', fxosApp: { name: 'Firefox Hello', manifestUrl: 'https://marketplace.firefox.com/app/54b83aea-1208-4605-82eb-22819f39d81d/manifest.webapp', rooms: true } }; 


PRIVACY & ToS LINKS - OK!

https://loop.services.mozilla.com
{
  "name": "mozilla-loop-server",
  "description": "The Mozilla Loop (WebRTC App) server",
  "version": "0.17.7",
  "homepage": "https://github.com/mozilla-services/loop-server/",
  "endpoint": "https://loop.services.mozilla.com",
  "fakeTokBox": false,
  "fxaOAuth": true,
  "i18n": {
    "defaultLang": "en-US",
    "lang": "en-US"
  }
}

Comment 4

[Mark Banner (:standard8)]

(In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #3)
> Mark, do you know if there are bug(s) for tracking problems related to
> video/audio not transmitting?  About half the loop calls I make seem to have
> this kind of issue.  It seems to be when calling specific users and
> unrelated to any particular deployment.  Not sure if device/network related
> or what's being done if anything to gather telemetry on this.

We have a few bugs around this. I won't be upset if you file a new bug.

If you get situations around where video is transmitting, but audio is not, then please capture the output of about:webrtc (latest builds have a save page option).

If it is about one-way connection, i.e. one side is receiving a black screen no audio/video, then its probably worth capturing about:webrtc and the room token (the bit after the first / and before the # if there's a #).

Comment 5

[Richard Pappalardo [:rpapa][:rpappalardo]]

(In reply to Mark Banner (:standard8) from comment #4)
> (In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #3)
> > Mark, do you know if there are bug(s) for tracking problems related to
> > video/audio not transmitting?  About half the loop calls I make seem to have
> > this kind of issue.  It seems to be when calling specific users and
> > unrelated to any particular deployment.  Not sure if device/network related
> > or what's being done if anything to gather telemetry on this.
> 
> We have a few bugs around this. I won't be upset if you file a new bug.
> 
> If you get situations around where video is transmitting, but audio is not,
> then please capture the output of about:webrtc (latest builds have a save
> page option).
> 
> If it is about one-way connection, i.e. one side is receiving a black screen
> no audio/video, then its probably worth capturing about:webrtc and the room
> token (the bit after the first / and before the # if there's a #).

This is really helpful.  It would also be great if on the 'What made you sad', the radio buttons were instead checkboxes.  Nearly 30% of the calls I've made to others had neither audio nor video transmitting.  Also, would we need to ask permission of Nightly,Aurora & Beta users to gather about:webrtc data and room # when they click on 'what made you sad'?   If that data is important, we should be collecting it automatically (if technically possible) from users that are experiencing that.

Comment 6

[Richard Pappalardo [:rpapa][:rpappalardo]]

> (In reply to Richard Pappalardo [:rpapa][:rpappalardo] from comment #3)
> We have a few bugs around this.
Also, since this is a known issue not specifically related to this release, I'm verifying this deployment.