Identity/WeeklyMeeting/2012-01-09: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:




= Dev =
<h1> Dev </h1>
Figured out the crash in {{bug|665057}} "Design and implement crypto API for BrowserID" - it is in a first-pass review. This code adds services/identity to mozilla central providing a chrome JS API to create keypairs for domains and create associated signatures
<p>Figured out the crash in <span class="fck_mw_template">{{bug|665057}}</span> "Design and implement crypto API for BrowserID" - it is in a first-pass review. This code adds services/identity to mozilla central providing a chrome JS API to create keypairs for domains and create associated signatures
</p>
<ul><li> <a href="https://github.com/mozilla/browserid/blob/train-2011.12.28/ChangeLog#L1-28">train-2011.12.28</a> in production</li>
<li> <a href="https://github.com/mozilla/browserid/blob/train-2012.01.05/ChangeLog#L1-10">train-2012.01.05</a> in staging</li>
<li> Primary support to be code complete this week.
</ul>


= Security & Privacy =
= Security & Privacy =

Revision as of 17:18, 9 January 2012

Last Week's Actions

  • Q1 goals by end of this week.

Major Progress

Dev

Figured out the crash in bug 665057 "Design and implement crypto API for BrowserID" - it is in a first-pass review. This code adds services/identity to mozilla central providing a chrome JS API to create keypairs for domains and create associated signatures

Security & Privacy

Ops

QA

  • Completed Train 16 in Stage:
    • Bug 711265 - please deploy browserid train-2011.12.08 to stage
    • Bug 711267 - QA and deploy BrowserID train-2011.12.08 to production
    • This train covered the move from Beta to the new Stage env
  • Completed Train 17 in Stage:
    • Bug 713961 - QA and deploy BrowserID train-2011.12.28 to production
    • This train includes changes to support winchan
  • Just started work on Train 18 in Stage:
    • Bug 715728 - QA and deploy BrowserID train-2012.01.05 to production
    • This train includes code (turned off) to support primaries
  • Working up some load-gen and graph monitoring documentation/wikis for QA team
  • QA action items
    • Client-side Selenium II automation: jrgm is taking this over
    • Work with Pete to finish up RPM install and configuration of QA environment (ID2)
    • Work with Pete to verify error logs, log rotation, and archiving in Dev and Stage

Engagement

Metrics

UX

Product

ACTION ITEMS