Closed
Bug 1119194
Opened 9 years ago
Closed 9 years ago
Please deploy Loop-Client 0.13.1 code to stage
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Assigned: dwilson)
References
Details
We'd like to deploy the loop-client 0.13.1 release to stage. https://github.com/mozilla/loop-client/releases/tag/0.13.1 We ideally want to deploy this today and Friday so we can get any feedback over the weekend before the FF releases.
Reporter | ||
Comment 1•9 years ago
|
||
No config changes at this time.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → dwilson
Assignee | ||
Comment 2•9 years ago
|
||
This has been released to stage https://loopclientstag-elb-1f0q67f2ah4or-549904786.eu-west-1.elb.amazonaws.com/VERSION.txt And dns has been repointed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•9 years ago
|
||
------------------ RELEASE NOTES ------------------ TAG https://github.com/mozilla/loop-client/releases/tag/0.13.1 RELEASE HISTORY https://github.com/mozilla/loop-client/releases https://github.com/mozilla/loop-client/compare/0.12.0...0.13.1 CHANGES 0.13.1 (2015-01-08) ------------------- - Backout string change from bug 1079227 - Update L10n to latest versions 0.13.0 (2015-01-08) ------------------- - Bug 1109032 - Fix initiating calls on FxOS so audio only calls from received links work - Bug 1097703 - Enable install/open FxOS Loop client from standalone UI for ROOM - Bug 1112021 - Remove drop shadows on Loop video elements - Bug 1105708 - More l10n compliant buttons for Loop - Bug 1114952 - Loop client extraction script fails to process all changesets on a merge cset (sometimes getting stuck), and is still a bit verbose for errors on no-issue changes - Bug 1112264 - Hide loop self-view with message if it would be incompletely shown - Bug 1109849 - Bypass the feedback form if no-one has entered the room yet - Bug 1000085 - panel.css and contacts.css should move to a non-shared directory - Bug 1096399 - Upgrade React to 0.12.2 - Bug 1118246 - Loop should handle forceDisconnect events from the OT sdk - Bug 1079227 - Loop feedback form should always allow comments - Bug 1117863 - Correct Loop's language fallback to use all of accept languages properly Config changes: - Added loop.config.fxosApp.rooms (not changed for this release)
Reporter | ||
Comment 4•9 years ago
|
||
------------------ QUICK CHECKS ------------------ SUMMARY placed a few test calls successfully using stage STAGE VERIFICATION https://call.stage.mozaws.net/VERSION.txt 0.13.1 d6d1518100d9f5c293ca7c524e3b264144ca945a Thu, 8 Jan 2015 11:38:38 +0000 $ curl -I https://call.stage.mozaws.net HTTP/1.1 200 OK Accept-Ranges: bytes Content-Length: 6056 Content-Type: text/html Date: Thu, 08 Jan 2015 18:24:23 GMT ETag: "54ae8724-17a8" Last-Modified: Thu, 08 Jan 2015 13:33:24 GMT Vary: Accept-Encoding X-Token-Match: 1 Connection: keep-alive https://loop.stage.mozaws.net/: { "name":"mozilla-loop-server", "description":"The Mozilla Loop (WebRTC App) Server", "version":"0.14.3", "homepage":"https://github.com/mozilla-services/loop-server/", "endpoint":"https://loop.stage.mozaws.net", "fakeTokBox":false, "fxaOAuth":true, "i18n":{ "defaultLang":"en-US","lang":"fr" } } https://call.stage.mozaws.net/legal/terms/ works ISSUES: Possible regression, the feedback form doesn't reset to the start a call page, after a call. Still investigating the issue.
Reporter | ||
Comment 5•9 years ago
|
||
(In reply to Mark Banner (:standard8) from comment #4) > Possible regression, the feedback form doesn't reset to the start a call > page, after a call. > > Still investigating the issue. Now filed as bug 1119485. I've agreed with Maire that its a small issue, and we are planning a release next Tuesday/Wednesday - and we have bigger issues to get fixed with this release. I've tested the rest and it is fine. Hence, marking as verified, we can go with the production push tomorrow.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•