ChangeLog including issues resolved: https://github.com/mozilla/browserid/blob/train-2011.12.01/ChangeLog#L1-27 [QA] Suggested areas of focus for QA: * Full regression testing! Absolutely everything given we're deployed in a completely new environment * Regression of all issues in changelog * Verification of RP sites beta.myfavoriteshow.org, beta.myfavoritebeer.org, and beta.myfavoritebooze.org * confirm IE8 is disabled, and IE9 works [RELEASE ENGINEERING]: * node 0.6.3! * Upon deployment, re-generate domain keys if not already RSA-2048 * Ensure npm install is run before `compress.sh`
Assignee: server-ops-labs → jbonacci
No longer depends on: 701934
QA Contact: zandr → jbonacci
NOTE: QA still targets the same URLs for testing, QA still has all the same expectations as before for what should work and our process. The difference is diresworb.org (our beta env) now runs in the ops "staging" environment, which is a completely new multi-node architecture. Our old beta VM is now idle and uneeded, and I'll offer it up to zandr to reclaim in a couple weeks.
This beta rolls with two known blockers. One is not expected to be a regression and might require no code changes: https://github.com/mozilla/browserid/issues/681 The other is a text-only cosmetic change in emails: https://github.com/mozilla/browserid/issues/684
expect hotfixes today.
Summary: QA and deploy BrowserID train-2011.11.17 to production → QA and deploy BrowserID train-2011.12.01 to production
QA accepts this train for testing. Initial environment checks and sanity tests all look good. Hot fix verification is done. Verification of Closed/Fixed issues is now in progress.
Status: NEW → ASSIGNED
Lloyd, according to the previous ticket (https://bugzilla.mozilla.org/show_bug.cgi?id=703596#c9 ) and IRC discussions, I was under the impression that we were not going to support IE8 for Prod or Stage. Here is what I see though: Prod: I can sign in and out on https://browserid.org (the UI looks a bit broken). I can not sign in on http://myfavoritebeer.org (as expected, and, again, the UI looks a bit broken): "We're sorry, but currently your browser isn't supported. BrowserID works with Firefox and other modern browsers." Stage: I can sign in and out on https://diresworb.org (the UI looks good here, as expected). I can sign in and out on http://myfavoritebeer.org (UI looks good here, as expected). So, was I mistaken and our intention was to block IE8 only on Prod?
Verification of Closed/Fixed issues continues... Also, verified "all-in-one" install on Mac using new required versions of node/npm.
QA has finished verification of Closed/Fixed issues. Focus now is on functional and compatibility testing across platforms, OS, browsers, etc.
QA signs off on Stage so that OPs can continue to beat on it. There are some important Issues that need to be investigated ASAP: 717: Android: Submit button not working, second tap results in empty assertion 708: can't sign-in with stock browser on android 704: Post animation callback not always called on Android default browser. And, a significant number of 4-stars that we need to focus on for the next train.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
This was deployed to Production with one HotFix: 727: Train 2011.12.01 hotfix 601: https://github.com/mozilla/browserid/pull/727
Verified the deployment to Prod: HotFix: 727: Train 2011.12.01 hotfix 601: https://github.com/mozilla/browserid/pull/727 https://browserid.org/ver.txt 8e04069 Add internal_api.js to the development includes. https://browserid.org/__heartbeat__ ok Code is updated New processes: /usr/local/bin/node /home/browserid/code/lib/keysigner/keysigner-compute.js /usr/local/bin/node /home/browserid/code/lib/verifier/verifier-compute.js New logs are being generated: browserid-error.log dbwriter-error.log keysigner-compute.log keysigner-error.log verifier-compute.log verifier-error.log Sanity Tests: Pass Verified myfavoritebeer.org, myfavoritebooze.org, myfavoriteshow.org, browserid.org One new issue: 739: old Dev/Prod: New "error" showing up in *-error.log files
Status: RESOLVED → VERIFIED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.