AMO:AOM Meeting:Firefox 4

From MozillaWiki
Jump to: navigation, search

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


March 3rd 2011

Mossop

Blair

Jetpack

Ecosystem

QA (Henrik)

Design

January 27th 2011

Mossop

  • Now down to 7 blockers for release
    • No hard blockers
    • ~3 that may not get fixed for release
  • 20 bugs fixed in the last two weeks
    • 11 blockers
  • Startup time instrumentation is reporting in

Blair

Jetpack

Ecosystem

QA (Henrik)

  • Verification work and creation of test extensions for Litmus and Mozmill tests

Design

January 13th 2011

Mossop

  • Now down to 8 blockers for release
  • Split blockers into hard/soft
    • Only 1 hard blocker left
  • Working on startup time instrumentation

Blair

Jetpack

Ecosystem

  • Dev Tools going live today.
  • Yay performance!

QA (Henrik)

  • A lot of new front-end bugs. What is the scope for Firefox 4?

Design

Remaining polish bugs have been nominated for soft blocking

January 6th 2011

Mossop

  • Quiet over the holidays, few blockers fixed but also very few filed.
  • Likely very little development for Firefox 4.next

Blair

Jetpack

Ecosystem

  • Compatibility moving along now that 4.0.* was added
  • Performance planning

QA (Henrik)

  • Not much happened except bug verifications
  • Will have to sit together with Vlad so we can bring the written manual tests into Litmus

Design

Some important polish fixes are needed on the manager, being tracked in bug 623250. Includes:

  • bug 623199 - Add-ons Manager global buttons (forward, backward, tools) should be contextually styled
  • bug 623207 - Add-ons manager last updated date and sorting bar should be removed from list view
  • bug 623211 - Add-ons manager add-on author name and link should be removed from list view
  • bug 623241 - Add-on notifications should be moved from the top of the add-on item to the top right of the list view items
  • (to be filed) - Sort add-on manager by status list view
  • (to be filed) - One click on each item in list view should launch description view

December 2nd 2010

Mossop

  • Sent the planning document off to the product drivers late last week.
  • Lots of stuff waiting to land but held up by broken trees

Blair

  • New theme landed (YAY)

Jetpack

Ecosystem

  • Disco pane details view landed but has some bugs to be worked out before going live.
  • Jorge blogged about icons in Firefox 4
  • Paid support?

QA (Henrik)

  • Tomorrow we will have our testday
  • 2/3 of the manual tests are already covered in the spreadsheet.

Design

November 18th 2010

Mossop

  • Post Firefox 4.0 planning document mostly complete, comments welcome: http://bit.ly/dcVaeH
  • Going to priorities bugs that block switching between restartless and non-restartless add-ons.

Blair

  • On PTO
  • Dao should be reviewing the UI changes this week

Jetpack

Ecosystem

QA (Henrik)

  • When can I expect work happening on bug 596343 - Upgrading to Firefox 4.0 should disable all third-party installed extensions
  • Testday on Dec 3rd!
    • We will have a prepared list of manual tests available (ongoing work with Waverly)

Design

November 11th 2010

Mossop

  • Blocker counts are dropping but could be faster

Blair

Jetpack

Ecosystem

QA (Henrik)

  • Litmus test creation outsourced
  • Feedback Input
    • As usual missing compatibility with add-ons (when do we bump the app version?)
    • No add-on search results when running search in a fresh profile (remote not activated) bug 611459
    • Empty extensions, themes, and plugins theme (beta 6 user?)
    • Add-ons disappeared during upgrade b5=>b7 (ACR, Adblock)
    • Missing download status when installing from AOM
    • Global restart and undo button missing
    • Slow loading of about:addons during start-up
    • Missing link to plugin checker page

Design

https://wiki.mozilla.org/AMO:AOM_Meeting/boriss_future_features

Firefox 4.1 Planning

http://etherpad.mozilla.com:9000/addons-Firefox-4-1-Planning

November 4th 2010

Mossop

  • Currently 6 blockers not in progress and unassigned (need to check up on the status of some of the assigned ones)
  • Probably going to close the meta-bugs down bug 550048 bug 461973

Blair

Jetpack

Ecosystem

QA (Henrik)

Design

  • Things wot need to be done:
    • Blair needs icon controls for inside of in-line download progress bar

October 21st 2010

Mossop

  • Nothing to discuss

Blair

Jetpack

Ecosystem

  • Discovery Pane has about 80,000 views a day in the beta
  • 21M featured list API calls are made per day (loading the Get Add-ons pane in 3.6 and below)
  • 1.3M searches from the API / Add-ons Manager

QA (Henrik)

Design

  • Open bugs:
    • General:
      • Having extension compatibility controlled on a per-addons basis bug 527861
      • Controlling order of add-ons in manager bug 595847 and adding a search plugin provider bug 552747
      • Allowing the user to pause installations bug 553024
      • Using Firefox’s download manager to manage add-on downloads bug 555753
    • Closed:
      • Allowing thumbnails and full-size screenshots to display in Detail View bug 553563
      • Assuring multiple copies of add-ons don’t appear in manager bug 562922
      • UX-centric functionality bugs for viewing add-on information
      • Giving a better experience for third-party installed extensions. Namely, to outright disable them on upgrade or not? bug 596343

October 14th 2010

Mossop

  • Updating and landing patches

Blair

  • Windows theme up for review, OSX theme in progress

Jetpack

Ecosystem

QA (Henrik)

  • Bug fix verification combined with some new bugs their investigation
  • Patch for Add-ons Manager for consistent naming of buttons
  • Planning to move out Litmus test creation

Design

October 7th 2010

Mossop

Blair

Jetpack

See jetpacks on AMO, now auto-tagged

Ecosystem

QA (Henrik)

  • Still working on the AddonsAPI for Mozmill - found some issues in the AOM code we would like to have fixed - already supplied patches
  • Having the first automated tests hopefully starting by tomorrow

Design

September 30th 2010

Mossop

  • Working through blockers

Blair

Jetpack

Ecosystem

  • Will start on other parts of the disco pane soon
  • Changing metadata ping grouping?
  • Disco pane loading states

QA (Henrik)

  • Spend most of my available time on updating the AddonAPI for Mozmill (bug 569813)
  • Will be digging through remaining b7 blocking verifications early next week
  • Immediately followed by adding more Litmus tests

Design

September 23rd 2010

Privacy Concerns with Metadata Retrieval

  • Currently pinging AMO once a day for metadata for all installed add-ons
    • Even multiple requests are potentially a concern
  • Spreading the requests over a longer period would be better

Mossop

  • Knocking out bugs
  • Checked over what is still remaining for the designs
  • Failed to triage the remaining blockers

Blair

  • Out sick

Jetpack

Ecosystem

QA (Henrik)

  • Testday last Friday wasn't such a great success but got a couple of bugs verified.
  • First 5 Litmus tests have been added. More to follow.
  • Updating the AddonsAPI for Mozmill to have some tests ready in the next couple of days (not sure how many we can have for buildbot because of external dependencies i.e. SSL pages)

Design

  • Monster status update: [1]

September 16th 2010

Mossop

  • Tying up for string freeze
    • Have strings in place for the marketplace
  • Hitting some issues with the search API
    • bug 597179 - Searching doesn't like "add-on"
    • bug 596771 - Retrieving data by GUID doesn't work sometimes

Blair

Jetpack

Ecosystem

QA (Henrik)

  • Testday tomorrow
  • QA has a bug week so we also will cover Litmus tests tomorrow

Design

September 9th 2010

Mossop

  • Finishing up b6 blockers, should be complete by end of week
  • HTTP hash header is supported in the nightlies
  • Extension packaging changes
  • HTML embedded in the API

Blair

  • Finishing up b6 blockers, should be complete by end of week

Jetpack

Ecosystem

  • Plugin updates gaining traction

QA (Henrik)

Design

  • Not much to report, have been on PTO & then was sick, lame
  • Item clearly missing: final screen for "Available Updates" pane, next priority
  • Question: can we create a way to remove items from Available Updates pane?

September 2nd 2010

Mossop

  • Dropped new appearance pane as the work is not containable for Firefox 4

Blair

Jetpack

Ecosystem

  • Discovery Pane front-end work in progress 99% done
  • Discovery Pane details view designs finished
  • Collections launch today

QA (Henrik)

  • We should have a quick check at all the open bugs which haven't been accepted/declined as blocker.
  • QA wants to start working on Mozmill tests. Have any patches landed which change the DOM of the Add-ons Manager? According from a talk with Dave on IRC yesterday - yes
  • Have to announce the testday on Sep 17th; will happen probably tomorrow.
  • Proposed to add [good first bug] whiteboard entries and call out for help
  • Will not be able to attend the meeting next week - being at CouchCamp

Design

August 26th 2010

Mossop

Blair

Jetpack

Ecosystem

QA (Henrik)

  • Manual updates: Missing items from mockups (bug 553503)
    • When do we want to show the "Available Updates" pane?
      • Only when updates are available.
    • Do we want to have the door hanger notification for the number of available updates?
      • Yes, we want
    • Do we want to show "Installing Updates" or the usual "Download" progress meter?
      • No, we will keep the Downloading progress meter
    • There is no "View Updates" link in the header after updates have been applied.
      • Not necessary
    • Should "Recent Updates" show extensions which haven't been upgraded yet?
      • No, only those which have been updated.
    • Which buttons should be visible in "Recent Updates" pane?
      • Release notes should be shown in details pane

Design

  • Design is gone next week! Oh god!
  • Emailing all graphic files & colors to the list before I leave
  • If you need graphic stuff next week that can't wait for the week after, email Steve Horlander

August 19th 2010

Mossop

  • Seem to be on track to get all b5 blockers done
  • May have about half of the new theme work done by the end of the week, all with temporary colours as we are still waiting on final values
    • New main view is about to go up for second review
    • New list view is about to go up for second review
    • New Detail view is awaiting review but already has a couple of necessary tweaks

Blair

Jetpack

Ecosystem

QA (Henrik)

  • vacation

Design

August 12th 2010

Mossop

  • Blocker counts are still too high but patches are in progress for a lot of stuff
    • I have patches for about 16 bugs in various states from mostly complete to waiting to land
  • New theme update targetted for end of next week
    • Main styling done ignoring specific colours
    • List view in-progress, mostly complete
    • Details view basically done
    • Appearance view has a few niggles around persona installation
    • All are pretty much blocked on needing more specific info from UX
  • The compatibility update on app upgrade UI is almost back (boo!)

Blair

Ben

Jetpack

Ecosystem

  • Decision on hash header for AMO installation

QA (Henrik)

  • Catching up after a couple of days of vacation, more vacation next week
  • Working to have a full list of Litmus / Mozmill tests by tomorrow, so we can start to add those after landing of the new theme.
  • We wanna have a testday on Sep 17th? If yes, I will schedule it

Design

  • Mockups for OSX and Windows are here
  • Priorities for today are mockups on:
    • Add-ons pending disable/enable/uninstall/etc look like in all views
    • Add-ons being installed in list view
    • How we represent backgrounds are not available when a theme is installed
    • Colors, textures, liberty, justice, and gradients for all

August 5th 2010

Mossop

  • Blocker counts are still high, but starting to drop
  • Appearance pane redesign is half complete
  • Getting ready for string freeze

Blair

Ben

Jetpack

Ecosystem

QA

Design

July 29nd 2010

Mossop

AOMBlockerChart.png

  • Taking on more blockers than we are fixing, this will hopefully drop
    • Have fixes for about 12 blockers awaiting review
    • All b3 blockers are either waiting to land, waiting to be reviewed or waiting for an updated patch after an initial review
  • Better undo support landed
  • Support for 30 personas landed
  • Details pane redesign is mostly complete, mostly waiting on mockups for other platforms

Blair

  • No updates

Ben

  • New mockups for search results list in Add-ons Manager (Bug 581084)
  • Working on updating AddonRepository to version to 1.5 of the AMO API, which adds a bunch of new fields

Jetpack

  • 0.6 launched this week, primarily bug fixes
  • Flightdeck 1.0a2 launches next week and then every 2 weeks until 1.0a4.
    • After 1.0a4, we start integrating with AMO
  • full notes here [2]
  • Jetpack 1.0 API proposal here [3]

Ecosystem

QA

  • Started working on the collection of Litmus/Mozmill tests
  • QA Test Automation will focus on Mozmill tests for the Add-ons Manager this quarter
  • Discussion for promoting the ACR extension for beta versions Google Groups
  • Next test-day planned for September

Design

  • If anything here [4] freaks you out, please say so... starting to get OSX together, blogging today.
  • Notable bugs this week:
    • bug 570012 Show download progress indicator when installing add-ons
    • bug 565522 Newly installed add-ons should be more prominent in about:addons UI

July 22nd 2010

Design

  • Backgrounds and Personas view
    • Proportions of backgrounds and themes in EM look much better similarly proportioned [5] than differently proportioned [6] - would cropping left side of backgrounds upset the community too much?
    • How to show when a background can't be used with a theme - could disable with a message such as [7] and [8]
    • Multiselection? oh god wut [9]
  • A few changes to list view [10] and details view [11]
    • Smaller categories on left more aligned to other areas of the future UI
    • Ratings probably not needed on list view - more of an expert feature, and we can't make it fully plugged into AMO for 4.0 anyway
    • Can we get a badness score in any useful way?
    • 128x128 icons in details view if available? [12]

Blair

  • Automatically updating restartless extensions - what if the user is actually using that extension when an update is downloaded and about to be applied?
    • All UI and functionality will disappear, then re-appear
    • Confusion, annoyance, and potentially dataloss
    • Can't detect when the extension is in use
    • Potential solutions:
      • Wait until idle (ie, the user hasn't done anything in the last 10 min)
      • Add API for restartless extensions to say when they can update
      •  ???
      • Ignore problem

Mossop

  • Assigned all blockers
  • Created a chart to track EM Blockers
  • Looking to finish up blockers for beta 3 over the next week
    • Proper undo support for restartless add-ons
    • Support for multi-package XPIs
  • How many personas to support at a time

Ben

  • Search results from AMO in the Add-ons Manager landed in time for b2
    • Remote add-ons show up along with local add-ons. Capable of filtering, sorting, and installing remote add-ons individually.
    • Detail view for remote add-on still needs work
    • Reorganize results, group remote add-ons together, and local add-ons together?
  • Working on upgrading AddonRepository to API 1.5
    • Is there a primary author? Author links?

Jetpack

Ecosystem

  • Need clarification on icons

QA

  • Verifications, verifications, verfications...
  • Questions
    • bug 581065 - Allow searching for incompatible add-ons if compatibility checks are disabled
    • bug 581103 - Search pane shows inconsistent search results from AMO

July 15th 2010

Design

Frontend

No code-related updates (I've taken most of this week off).

From the summit:

Backend

  • Working on compatibility updates during application upgrade and undo support
  • Reviewing Ben's work
  • Pushed off a number of beta2 blockers
  • Skimming over Feedback results:
    • Add-ons are incompatible
    • No install confirmation (fixed)
    • Buried under the new Firefox button (bug 579176)
    • Incompatible default theme (bug 579170)
    • Need restart to install add-ons still (Jetpack FTW!)
    • Cannot undo uninstalls

Jetpack

Ecosystem

QA

  • Working on verifications in the next days
  • Start to collect information for Litmus and Mozmill tests
  • For which beta we want to block bugs which external communication

June 24th 2010

Design

Frontend

Backend

Jetpack

Ecosystem

QA

  • Verification of fixed bugs
  • A compatible version of the ACR needs to be uploaded to AMO for beta 1
    • Justin will send an email to Brian

June 17th 2010

Design

Frontend

  • Manual update interface coming along.
    • Hampered but not hard blocked by some API issues (eg, bug 562599, bug 553966).
    • Assuming code freeze is tomorrow, this probably won't make it, due to lack of polish and lack of tests.

Backend

  • Hacking on bugs

Jetpack

  • 0.5 is going to get a big announcement
  • 0.6 will start to move to the generic add-ons branding
    • Flightdeck is going to be super awesome

Ecosystem

  • Rocket your Firefox contest at the summit
    • Three prizes

QA

  • Successful Add-ons Manager testday - 11 bugs have been found
  • Make sure that all fixed bugs get verified before the code freeze
  • Updated testplan spreadsheet for ACR extension in co-work with Brian
  • Need feedback from Dave and Blair for their tables on the spreadsheet
  • Status of beta1 blockers
  • Links on Discovery Pane point to services.addons.mozilla.org
  • Have to household with my time the next two weeks - fully back next quarter

June 10th 2010

Design

  • Working on final graphics - been meeting with Stephen Horlander to sync up on in content design
  • In-progress mocks here
  • Anything needed for beta?
    • Background loading
    • Cheats for removing restartless add-ons

Frontend

No updates. Getting back into this starting today.

Backend

  • Patched bug 565610. It is waiting on review but it is now a beta 1 blocker.
  • Worked on some error handling cases and will have proper error messages for some of broken-download cases soon.
  • Partial fixes for some of the main chrome UI while the add-ons manager is visible.

Jetpack

  • 0.5 will be out June 23rd
    • Includes panel and tab APIs
    • Maybe accelerating sidebar API

Ecosystem

  • Discovery Pane designs being updated by Martell. If we get them this week, we should be able to implement by the beta at the end of the month.

QA

Addons Manager and Extension API
  • General
  • Upcoming Schedule
  • Questions
    • Do automated tests interact with ui elements?
Discovery Pane
    • No update

June 3rd 2010

Design

Mocks added to bugs:

Main focus is now on final graphics unless there are other major bugs that need consideration (anyone?). Final graphics are not done, some initial mockups are here

Other bugs (rdoherty)

  • bug 550628 Add "don't show this again" to persona install notification
  • bug 570012 Show progress indicator when loading a persona

Frontend

  • Started work on Manual Updates stuff - work is dependent on having free time from AppTabs
  • No string freeze for first beta, but aiming for code-freeze on 18th (only 2 weeks away)

Backend

  • Rolling on with the documentation. Larger parts are complete but still a couple of important pages to do.
  • Talks about removing or curtailing support for add-on installs by third party apps.

Jetpack

  • SDK 0.4 released with cool new features
    • Mailping demo extension shows your mail counts
  • SDK in planning
    • E10S support
    • Panels displaying over content
    • Probably the last version that will be 3.6 compatible

Ecosystem

  • Fligtar to talk to Sean to work out the timescales for disco pane designs.

QA

Addons Manager and Extension API
  • General
    • Will also cover these projects:
      • Pull More AMO Data into Addons Manager
      • Addons Compatibility Reporter
  • Testplan: Working on a tracking spreadsheet
  • Bug Queries have been updated
  • Upcoming Schedule
    • Waiting for arrival of final mockups June 4th
    • Next testday is on June 11th
  • Questions
    • Bugs: bug 565610 - Importance of overlaying about: urls
    • Bugs: Handling blockers for additional betas vs. final
    • Languages: Which specific features we will support? (Install/Uninstall/Switching?)
    • Jetpacks: Do we officially use the name Jetpacks or restartless extensions?
    • Jetpacks: Can those be installed system-wide (app folder, registry)?
    • Jetpacks: Can we get an example Jetpack on AMO
    • UI: Usage of modal dialogs (Beltzners Fx4 presentation); e.g. bug 567120
Discovery Pane
    • No update

May 27th 2010

Design

Frontend

  • Blair has been working on automated tests for the UI

Backend

  • Made plans with bsmedberg to remove the EM restart during startup
  • Catching and fixing some bugs critical for the next alpha release
  • Started work on the documentation, slow going but getting there

Jetpack

  • E10S support in Jetpack possibly in 0.5 or 0.6 release.
    • Will allow for isolating perf impact of add-ons individually
  • Invisible Hand already ported to Jetpack
  • WOT likely next on list

Ecosystem

  • Currently exploring a variety of payment options with emphasis on security and user experience

QA

Overall
  • General
    • Do we wanna have bugs for the implementation of each of the mockups?
    • TODO: Sync mockups with testplan next week
  • Testing
    • Keeping up2date with verification work
  • Schedule
    • Waiting for arrival of final mockups June 4th
    • Next testday is on June 11th
Discovery Pane
    • Clearing out communication issues

May 20th

Design

Remaining stuffs is getting done, such as:

Dave made a helpful list of most important bugs, next priorities are:

O here are In content UI first mockups

Frontend

  • Blair has been working on automated tests for the UI

Backend

  • Prioritised the bugs needed for release

Jetpack

  • E10S support in Jetpack possibly in 0.5 or 0.6 release.
    • Will allow for isolating perf impact of add-ons individually
  • Invisible Hand already ported to Jetpack
  • WOT likely next on list

Ecosystem

  • [13] Lots of interest here both internally and externally
  • Some stats: 12% of public Fx add-ons ask for contributions, average revenue per add-on is about $130 but top 3 add-ons comprise 15% of all contributions.
  • Currently exploring a variety of payment options with emphasis on security and user experience

QA

Overall
  • General
    • As sent-out by Dave we need final Mockups ASAP. When will those arrive? (June 4th)
    • Talk about the best way to prioritize bugs for next alpha or beta1
    • Do we still need the bug dependencies and whiteboard entries?
    • Correct components for existent bugs (right now nearly all are in addons manager)
    • Search Engine pane should be hidden (bug 567115)
  • Testing
    • Finished verifying all fixed bugs.
  • Schedule
    • Next testday is on June 11th
  • Litmus
    • Compiling list of Litmus tests.
Discovery Pane
    • No update

May 13th

Design

Frontend

  • bug 565610 - Overlays don't work on about: URLs - deal-breaker for EM-related extensions. Should be fixable.

Backend

  • Re-landed on trunk and working through the remaining issues
  • Saw about a 1s Ts improvement for the Fennec guys
  • First startup and migration startup times can be vastly improved

Jetpack

Ecosystem

QA

Overall
  • General
    • Now that a lot of ui bugs have been fixed, Blair should check the in-testsuite flags. I do not wanna do Litmus work when it can be automated.
  • Testing
    • Started verification of fixed bugs
  • Schedule
    • Planning for exact schedule for the next testday
  • Litmus
    • Starting to add new Litmus tests by next week
Discovery Pane
    • No update

May 6th

Design

  • Really not much done this week - a few bugs, more to go through

Frontend

Backend

  • The source of the Ts regression has been found, working with IT and Releng to figure out when we can reland.
  • Fixed some of the more obvious functionality errors found at the testday
  • Investigating a couple of bad cases that I can't reproduce yet.

Jetpack

Ecosystem

QA

General
  • Testday
    • Results
    • Successful testday last Friday (55 bugs have been filed)
    • Found blockers for localized builds
    • A lot of ux related bugs have been filed; needs to shrink the uiwanted queue
  • Tests
    • No overall testing this week; waiting for feature re-landing
    • First accessibility tests showed good results
  • Schedule
    • ETA for final design? Wonder if all ux members work together to give any part of the ui the same look; AMO design is made for Mac but not for Windows as all the other designs; makes it hard to compare.
    • As proposed by Mike the search pane should be included in beta 1
  • Add-ons Compatibility
    • Will there be tutorials for Add-on developers to make their life easier in updating their add-ons?
    • Will we have a stable Jetpack API for beta 1 or are other breaking changes expected?
    • Mike wants to see people create Jetpacks instead of oldish extensions for RC1
Discovery Pane

April 29

Landing

  • Can we? Pretty please? I'll give you a cookie!
    • Yes, now where's my cookie?
      • Can I have one too? Plz?
  • Mobile has branched - don't need to worry about breaking it now
  • SeaMonkey is shipping an alpha soon (based on trunk). They'd like consideration for holding off til the 4th if we don't land today, but its not a big deal if we don't.
  • Development plans for post-landing
    • Usual file bug, attach patch, get review, land - but on project branch? Or on mozilla-central?

Design

  • Knocking off some ui-wanted bugs
  • Balance time between fire fight & new - what do people need?
  • Starting to work w/Shorlander on final graphics

Frontend

  • Text describing the Contribute button (ie, its tooltip) - what should it say? (Disclaimer: doesn't actually work yet)
    • Should say "If you enjoy using <addon name>, please consider making a small contribution to the developer"

Backend

Jetpack

Ecosystem

QA

  • Issues
    • Top Issues
    • bug 554234: We have changed the behavior and only allow one single addons manager tab open?
    • bug 465090: Keyboard shortcut to open the addons manager?
    • bug 562360: Compatibility information for add-ons on preview.addons.mozilla.org are not in sync with public pages (Mozmill Tests)
    • Purpose of "Your Rating"? We don't share ratings? Missing documentation on design docs
    • uiwanted bugs should be processed. We have to many of them.
    • State of a Jetpack example?
  • Trunk landing
    • Needs to have localized nightly builds (localizers will help testing)
    • We have to spin new nightly builds after landing (releng is informed)

Personas

April 22

Design

  • Changes to manual update Manual update addons234.png

Frontend

Backend

  • 2 reviews remaining, at least one should be done by the morning, hopefully the other too. Basically ready to land.
  • Next alpha freeze is at least a week away and could be pushed back further at our request.
  • May have to delay landing for the mobile team though.

Jetpack

Ecosystem

QA

  • Top Issues
  • Testing
    • Continued testing of branch builds and filed bugs
    • Reduced testdays to only Friday next week
  • Questions
    • What happened with the Get More Extensions/Themes links? We should linkify AMO from within the addons manager
  • Others
    • Please use bug numbers in the commits for your check-ins
    • Henrik is away this Friday and Monday

April 15

Design

- some changes to wiki regarding manual install and checks for updates: link

- don't want to take up time with manual check/install case again unless people are interested, but details are in bugs bug 553503 and bug 553502

- did want to bring up Download Manager changes: Download Manager is becoming a record of all files download, even updates for Firefox and Add-ons. I think this could take the place of an in-addons-manager log. It's already going to be listed within the Downloads Manager, so we'd need to create a second log in add-ons already (can updates be "undone" from Download Manager?)

- just planning hard and soft blocks (two levels, not three) as a third has not been identified as needed. Soft block creates an extra screen in install process explaining risks, hard block shows screen explaining before install. (Question for Nick - should hard blocks be overridden for any case?)

Frontend

  • First round of reviews done - not expecting anything big from 2nd round
  • Just a few landing-blockers left

Backend

  • Main reviews are done. Waiting on additional reviews for a couple of parts from bsmedberg and dveditz
  • Couple of bugs I still need to complete but they should be fast

Jetpack

Ecosystem

  • Discovery Pane scaffolding and prototype milestone started Tuesday

QA

  • No updates - waiting for fixes
  • Link to the Blocklist documentation?
  • Plan for trunk merge? Dave will speak to Benjamin about the next freeze.
  • Working through remaining ui-wanted bugs?

April 8

Design

  • Blocklist for next week:
    • Hard block and soft block currently supported, the API would support a third
  • Talked about manual updates, if a log is requires
    • Decided a log is important, and so is being able to easily apply manual updates
    • Requires updated design: current "Updates" pane that shows both could be confusing

Frontend

  • Lack of progress due to holidays and sickness
  • Initial review went well - almost done and ready for next round
  • Still some blockers left to do (eg, bug 553515, bug 554245, bug 553631, and unbreaking existing tests)

Backend

  • Undergoing final round of review for the first trunk landing
  • Couple of small bits and pieces to fix up before that
  • QA have identified some issues and we'll need to prioritize them

Jetpack

Ecosystem

QA

  • Top Issues
    • bug 557956: No compatibility updates downloaded when version gets bumped up
      • We should block at least for the compatibility check. Further work can happen after trunk landing
    • Which is the list of blocking bugs for trunk landing?
      • All blocking bugs are handled with the P1 priority flag. There are 61 bugs => Needs re-prioritization
  • Current status
    • Tchung dropped of from testing
    • First draft of the testplan is available
    • More testing on recent branch builds
  • Questions
    • Will/Can the top search bar also search for available addons (disabled checkbox in search pane)?
      • For now, searches will only be run locally. Remote searching will land after the trunk merge. bug 558287
    • Will the new preferences pane break all addons which come with a preference dialog?
      • We will allow existing preferences dialogs; In the list view you can open it via the context menu; Extra button for detailed view?
    • Which features will the search engine pane be able to handle for Firefox 3.7?
      • Work will not happen before trunk landing; All features should be included in the final version; Blair will probably work on it => bug 558289
    • Is there a way to fetch add-ons from AMO without increasing the download numbers?
      • Yes, we should use the preview site instead of the public one.
    • When do we start to support Jetpacks on AMO?
      • Scheduled for same version as the Discovery Pane landing; We could upload Jetpacks to the preview site
    • How many instances of the Add-ons Manager tab do we allow?
      • Multiple tabs per window
    • Can Jetpacks and Personas get blocklisted too?
      • Only Jetpacks
    • Do we have documentation for blocklisting?
      • Dave will find the best docs for me
    • When we could consider to have the first accessibility tests?
      • Probably after landing on trunk
    • When can we walk through all frontend bugs to identify automated/manual tests?
      • Sometime after trunk landing
    • Do we have a final solution about handling add-on dependencies?
      • It will be dropped

April 1

Design

Frontend

Backend

Jetpack

Ecosystem

QA

  • QA has to finish work for Q1 goals / security releases
  • Henrik will work on the test plan next week; Date for the test plan review needed
  • Retornam created initial testplan for the Discovery Pane]
  • Testdays scheduled for 04/27, 04/29, 04/30; Wednesday is free to allow Dave/Blair to fix found problems.
  • Next 3.7 alpha is dumped to after the chemspill releases - should we wait with the merge?
  • Discovery pane: which devs will work on the discovery pane? Can we get a tracking bug?
  • Discovery pane: solution yet for opt-in or opt-out for sending information?

March 25

Design

Frontend

Backend

  • Fixing bugs that block Blair
  • Addressing review comments
  • Current estimate is a trunk landing early next week

Jetpack

Ecosystem

QA

  • Tony already tested and filed a couple of bugs
  • Henrik stepped through all filed bugs
  • Next or 1st week in April we will enhance the test plan to add more details
  • Start verifying bugs after landing on trunk

March 18

Design

  • Faaborg is keen to explore add-on performance and how to show this in Firefox UI.
  • design

Frontend

  • Install/update/uninstall/enable/disable done (some tweaks & fixes needed)
  • Catching up with mockup changes
  • Not quite ready for review / m-c landing

Backend

  • Still need to add plugins to the API but otherwise all main tasks are complete
  • Restartless add-ons are working!!
  • Bulk of the API work has been submitted for code review
  • Need to talk about Q2 goals

Jetpack

  • Jetpack team wants 'no restart' in some 3.6.* release, mossop is exploring

Ecosystem

QA

  • Initial test plan created
  • Proposed to use the [fixed-in-addonsmgr] whiteboard entry for all fixed bugs on the addonsmgr branch A: Yes, its being used now.
  • Links for Prioritized Goals and Redesign Themes should be added as sub pages under the current project page (still on the outdated page)
  • Search results pane is only displayed after a search has been performed? A: Will it get hidden again? yes, it gets hidden.
  • Will the search engine manager now be a part of the addons manager? A: yes.
  • Do we take care about accessibility for the new ui? (marco zehe can help) A: yes, need to have a meeting with Marco at a later time.
  • Is the order of the pane listing on the left side the final one? Shouldn't we order the items from highest to lowest prio, e.g that search pane is not injected in between get addons and languages, which causes other entries to move down. I would like to see a final list and order of those panes. A: Not the final list.
  • Given by johnath the addonsmgr branch should be merged as early as possible to trunk even when QA is not ready with testing. conflict with code freeze for a4? henrik has sent an email to benjamin. A: will not make it into alpha 4. plan is to goto trunk end of next week, but pending early test results.
  • Temporarily tracking top issues here, before bugging them. https://wiki.mozilla.org/QA/Firefox_3.next/Test_Plan:AddonsManagerRedesign#Tracking_Issues

March 11

Design

Frontend

Backend

  • Webpage installs hooked up and working
  • Project branch set up and ready to receive checkins for testing
  • Will be doing perf testing over the weekend and planning out the trunk landing next week

Jetpack

Ecosystem

QA

March 4

Design

Frontend

Backend

  • Working on installs from webpage, need input from the platform guys.

Jetpack

Ecosystem

QA

February 25

Design

Redoing wiki, taking care of some edge cases, specifying how jetpack/extensions and personas/themes work together

Frontend

Nothing exciting. Solidifying code, enable/disable, etc.

Backend

In the process of making installs from webpages work, this is the main blocker I have before we could consider a trunk landing.

Jetpack

https://wiki.mozilla.org/Labs/Jetpack/Reboot/JEP

Ecosystem

  • Updating add-on review process so add-ons can't stay in sandbox forever

February 18

Design

Frontend

No update.

Backend

Considering removing the callback option from InstallTrigger.install

Jetpack

Ecosystem

February 11

Design

Frontend

  • Download progress widget done. Should be possible to do a fancy button -> progress transition.
  • Local search done - including sorting based on relevance to search string
  • AMO search not done - need API support and UX details

Backend

No update, no Mossop.

Jetpack

Ecosystem

February 4

Design

Frontend

Working on getting UI up to speed with Boriss' mockups.

Getting it on trunk:

  • Want it on trunk sooner (alphas) rather than later (betas)
  • Project branch
  • Maybe land without major AMO integration? (use followup bugs)
  • UI doesn't need to be pixel-perfect or even finalized (again, use followup bugs)
  • Minimum: needs to be able to manage addons

UI qustions:

  • Discover pane - complement or replacement of Recommended?
  • Want a way to display multiple screenshots?
  • Lots of white-spece between relevant things on larger screens (looks great on small/medium sized screens)
  • Link to AMO developer profiles - what about multiple developers, that install.rdf doesn't list?
  • Detail view at https://wiki.mozilla.org/Extension_Manager:UI_Update_questions isn't very detailed - only adds screenshot (compared to list view); not much value, no incentive to go there

API questions:

  • Should API be caching remote resources like screenshots?
  • With AMO integration, addons not hosted on AMO will have sub-par experience. add support for additional things like screenshots to install.rdf?
  • Status of install/update stuff?

Backend

No update

Jetpack

Ecosystem

January 28

Design

  • Been making some changes to the design (not too major), in light of feedback & talks with ux
  • Been answering unsure/unanswered questions, many of which graciously supplied by Mossop (Q&A style going on here.)
  • Rewriting wiki, getting rid of superfluous stuff - want to make it clear what design is current
  • Did random blog post, am getting good feedback
  • On Monday, UX is doing lockin session on Prefs and EM - these tend to be six hour design sessions where we hash out everything, look for dependencies, fight!
  • Items I'd like to discuss:
    • Personas vs. Themes - especially after seeing Personas post mortem, this seems a bit pricklier than I'd even imagined. How are we thinking about these? Is it decided? What do we have to go on before going ahead on a design?
    • Jetpack - where are we now that 3.6 has shipped? Do we know anything new

Frontend

No update.

Backend

No update

Jetpack

Ecosystem

  • Question: what is the plan for uplifting personas plus UI into Firefox?

January 21

Design

  • Small changes to existing mocks in wiki, as discussed last week
  • A few new mocks, but not yet on the wiki (bad bad!), will add tonight
  • Looked at notification styles, trying to align what we tell the user and when, and how we can do less of it. Have a working model of omg (priority 1, can't be dismissed), ok (action is required, but not now, and you'll probably do it anyway), and eh (something happened that you don't care about). I'll explain more in the meeting.

Frontend

No update.

Backend

  • Worked on being less restrictive about what html developers can use in their release notes

Jetpack

Ecosystem

January 14

Design

  • latest from Boriss, hooray!
  • Nick wants contributions in the mocks, here's some metadata to consider
    • link to contribute going to AMO meet the dev page
    • dollar amount
    • buy vs contribute
  • Feedback from fligtar
    • We can consider getting add-on status data from AMO along with reviews and downloads, and show whether add-ons are reviewed by Mozilla or not reviewed by Mozilla (experimental, self-hosted, and non-hosted add-ons)
    • We should change Recommended to Featured
    • Not a fan of the name Features for add-ons
    • Should be more distinction between My Add-ons and browsing for new add-ons
    • I don't think size information is useful or important to display on every add-on
    • I don't think we need to worry about integrating collections for 3.7. The Add-on Collector will add sections for Personal Recommendations and Collections to 3.7 and we'll be changing the way collections works considerably this year. Perhaps it will be stable enough for core integration for 4.0

Frontend

Note: That's on OSX. Needs tweaks on Windows (and probably Linux) to make it look not ugly.

Backend

  • Produced list of requirements from AMO API
  • Removing support for extension dependencies.
  • Tweaked some of the notifications to better suit add-ons that don't require restarts.

Jetpack

Ecosystem

January 7

Design

  • Boriss furiously slapping together mocks, will post to wiki

Frontend

  • Blair working on initial prototype of EM in content

Backend

  • Mossop to provide suggestions for changes to API as we rewrite services.amo

Jetpack

  • Jetpack rewrite happening which will allow authors to write jetpacks and build them into standard extensions

Ecosystem

  • AMO being rewritten in Python/Django
  • API update in February will feature add-ons by locale (currently all browsers get the US feed)

October 29

  • Boriss has created mocks to show in content
  • Todo: start looking at how to blend different types of add-ons into a single list, and incorporate AMO metadata
  • Mossop still working on 3.6 blockers, should start work on API stuff next week.
  • Johnath and Gavin coming next week, will sync up on prefs + EM work

September 17

Personas

Plugins

  • Adding rudimentary ways to check for plugin updates to the add-ons manager. See the screenshots in bug 514327. Checking for updates loads a webpage that will explain how to update.

September 10

Design concepts needed

  • Contributions
  • Reviews (both read and submit)
  • Better, friendlier browse experience
  • Personalized Recommendations
  • Performance gauge

Personas

  • Will land in 3.6, not in minefield yet. Hopefully we'll be able to see this integration next week

Timing

  • We should start having this meeting weekly, and set goals with the intent of including a new add-ons manager in 3.7
  • Naming of the add-ons manager may change with the goal of creating greater awareness of add-ons (e.g. "Firefox App Store")
Retrieved from "https://wiki.mozilla.org/index.php?title=AMO:AOM_Meeting:Firefox_4&oldid=293650"