AMO:AOM Meeting

Please visit the Add-ons wiki pages for up to date information.

AMO Project Meeting Details

Thursdays, 2:30pm Pacific, 4:30pm Eastern
1-800-707-2533 (pin 369) or 1-650-215-1282 or 1-650-903-0800
Conferencing Center: x92
Conference ID: 366


Oct 6th 2011

Projects

Development updates

  • Labs kit breaking updates

Ecosystem updates

QA updates

Please review and give feedback on current Updates testing strategy

Sep 8th 2011

Aug 25th 2011

Projects

Development updates

Ecosystem updates

QA updates

  • Working through remaining bug verifications as best as possible
  • Once Vlad is back from vacation we will work on test plans for all the features

Aug 11th 2011

Projects

Development updates

Ecosystem updates

QA updates

  • Due to team reorganizations in QA Henrik will be replaced by Vlad Maniac (Softvision) for the QA lead position of the Add-ons Manager project
  • Updated Extension Manager QA page with Semantic MediaWiki queries
  • Right now working on bug verifications for Aurora and Nighly
  • Planning extensive testing of 3rd party add-ons patch in the next days

July 28th 2011

Projects

Development updates

  • Chrome registry support for restartless add-ons landed, bounced, mak is looking to fix

Ecosystem updates

QA updates

June 30th 2011

Projects

Development updates

  • Chrome registry support for restartless add-ons

Ecosystem updates

  • Add-on compatibility going forward

QA updates

  • Nothing major happened in the last 3 weeks due to vacation.
  • Signed off from Firefox 5 and Firefox 6 beginning of June
  • Expected sign off from Firefox 7 features planned by Monday
  • Firefox 8
    • When do we start planning for features?
    • Moving over not landed features
    • Will keep up with creating test plans once features have been selected
    • Closer communication possible between meetings, updates via email?

May 19th 2011

Projects

Development updates

Ecosystem updates

QA updates

May 5th 2011

Projects

Development updates

  • Get Add-ons loading screen tweaks
  • Intern on the way

Ecosystem updates

QA updates

April 7th 2011

Projects

Development updates

  • People are seeing the add-ons manager hang on Linux bug 637286 - fixed and awaiting branch approval

Ecosystem updates

QA updates

  • Planning on creating the test plan for Firefox 5
  • Mozmill test creation for this quarter (start with restart tests)

March 29th 2011

New development cycle

  • mozilla-central -> mozilla-experimental -> mozilla-beta -> mozilla-release
  • All new code lands on mozilla-central first
  • Code spends 6 weeks on experimental/beta channels before hitting release
    • Small low risk fixes can be taken directly on these channels
    • Larger problems mean turning off the new code and waiting for the next cycle
  • Users get silent updates and can change between channels
  • Checkins for Firefox 5 must be high-value, low-risk, easily removable
    • Feature priorities for sure
    • Stability fixes
    • UI tweaks, if they are low risk
    • API fixes if they are high value for extension developers
  • Using some whiteboard entries for tracking bugs:
    • [wanted fx5] for bugs we probably want to get fixed soon and would take for Firefox 5
    • [can land fx5] have patches that are ready to land and meet the criteria for Firefox 5
    • [can land fx6] have patches that are ready to land but don't meet the criteria for Firefox 5 and so will likely slip to 6

Projects

Development updates

  • People are seeing the add-ons manager hang on Linux bug 637286

Ecosystem updates

QA updates

  • We have a couple of open in-testsuite requests or even bugs without any request for a manual or automated test. How do we want to handle those bugs?
  • About 40% of manual tests have been added to Litmus. Working on the remaining ones in the next couple of days.

Archived pages