683922 - QA and deploy BrowserID train-2011.09.01 to production

Status: VERIFIED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Labs, task)

Description

[Shane Tomlinson [:stomlinson]]

ChangeLog including issues resolved: https://github.com/mozilla/browserid/commit/f992fa9544630d03c2d6177cf70a0fda01c44918#L0R1

[QA] Suggested areas of focus for QA:
  * Verify that incorrect login credentials shows an error message.
  * Verify that Chrome has no problems syncing multiple email addresses.
  * Make sure that email addresses are synced when going to manage page.
  * Keep up the push on mobile/non-Firefox desktop OSs.

Comment 1

[James Bonacci [:jbonacci]]

Going forward, can we post the Dev Unit Test results in this ticket each week?
A link to the actual results is sufficient.
Long term, it would be good to post the results of Unit Tests (or similar Dev tests) running against Beta before it is released to QA.

Reviewed all new and open issues for this week.

New/Open bugs for this week:
230: use $.bind or create a wrapper for addEventListener on myfavoritebeer
231: Set up dev "browserid" servers to use HTTPS to mirror prod environment
232: New accounts: Login string and logout link are "invisible" on beta.myfavoritebeer.org
233: Opera on Mac: Tabbed UI vs. pop-up results in inability to log into beta.myfavoritebeer.org
234: Would be nice to have date/time stamps in BrowserID logs
235: The submit button looks weird on iOS
236: BrowserID sign-in form activates the keyboard on iOS
237: call window.focus() on the popup window
238: Long usernames cause MyFavoriteBeer to push username onto next line.
239: dialog messaging ui nit when creating account with an existing address
240: verify on myfavoritebeer uses CORS request, which IE8/9 cannot do.
241: set the meta viewport tag in the browserid dialog for mobile browsers
242: make sure only one relay iframe is ever created
243: Make sure that browserID can be opened/used through multiple logins without calling page reload.
244: Generating multiple keys causes IE8 to display an "unresponsive script" warning.
245: RP in repo uses CORS which IE cannot do
246: using StealJS in dev mode causes IE8 to not load the BrowserID Dialog
247: browserid/static/include.js: if message is not in JSON-string format
248: IE8 gives missing JSON error on browserid.org
249: IE8 shows text under BrowserID logos

Verified by QA:
219: /ws_api/set_key always returns returns value instead of HTTP 204 response
222: incorrect initial authentication is not displaying error message.

No QA verification needed:
update javascript mvc to 3.1.0.
major interframe/window communication change using a hidden relay iframe to facilitate IE: #97(still open)

Verified as still open:
227: link colors on browserid.org are consistent


Beta Processes:
www-data 11338  0.0  1.6 632368 16400 ?        Sl   Sep01   1:15 /usr/local/bin/node /home/browserid/code/verifier/run.js
www-data 13497  0.1  1.8 701756 19000 ?        Sl   08:14   0:41 /usr/local/bin/node /home/browserid/code/browserid/run.js
Is there a reason why this date/time stamp is newer than 9/1?

Versions:
Prod: aefe662 integrating train 2011.08.25 
Beta: 8c98ecb Removal of experiment of x-frames-header.
Dev: 3ef380e Instead of using `color: transparent`, using `font-size: 0px`

Logs: browserid.log 
Seeing the following (infrequently) - are these expected?
warn: CSRF validation failure: POST only allowed to /wsapi urls.  not '/commit_made'
warn: CSRF validation failure: POST calls to /wsapi require an active session

Mobile-based testing continues for this train.

QA is looking forward to testing mobile, IE 8/9, and the new UI!...

Comment 2

[James Bonacci [:jbonacci]]

QA signs off on this train.

Comment 3

[James Bonacci [:jbonacci]]

The 09-01-2011 train was successfully deployed to Production.