Firefox/Planning/2013-04-24
Jump to navigation
Jump to search
« previous week | index | next week »
Full Query Google
Planning Meeting Details
- Wednesdays - 11:00am PT, 18:00 UTC
- Mountain View Offices: Warp Core Conference Room
- Toronto Offices: Finch Conference Room
- irc.mozilla.org #planning for backchannel
- (the developer meeting takes place on Tuesdays)
Video/Teleconference Details - NEW
- 650-903-0800 or 650-215-1282 x92 Conf# 99696 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 99696 (US)
- Vidyo Room: ProductCoordination
- Vidyo Guest URL
REMEMBER
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.
Actions from Last Week
Schedule & Progress on Upcoming Releases
Firefox Desktop
Current Releases
Beta (147)
- We Shipped FF21.0b3 last week
- FF 21.0b4 went to build yesterday, planned to release before Friday.
Aurora (54)
Nightly (148)
Firefox Metro
Metro Highlights
- Iteration #5 - Completed
- Team completed 75 story points across 25 features - a 19% increase in performance from the previous iteration.
- Team established a new average velocity rate of 47 story points per iteration - a 17% increase in performance from the previous iteration.
- Overall performance gain in story points and velocity resulted in a new production forecast release of December 23, 2013 - a reduction of 3 iterations from the previous release update.
- Product Manager review of V1 Release List resulted in the removal of 9 Feature Stories to V2.
- Iteration #6 - Current
- 5 resolved stories awaiting verification testing.
- 4 Sync related feature stories were reopened following testing.
- Product Manager is reviewing the Story Backlog and reprioritizing feature stories for the upcoming Iteration #7.
- Status reports, starting with Iteration #6, will now present three release forecast scenarios: Worst, Expected and Best case.
Iteration Performance Summary
- Total Work: 109 total story points - 27 bugs.
- 16 feature stories.
- 9 defect stories.
- 2 change stories.
- Completed Work: 36 story points closed - 14 bugs - 33% complete.
- 5 feature stories.
- 8 defect stories.
- 1 change story.
- Remaining Work: 73 story points remaining - 13 bugs - 67% open.
- 11 feature stories.
- 1 defect stories.
- 1 change story.
Iteration Work Details
28 Total; 0 Open (0%); 8 Resolved (28.57%); 20 Verified (71.43%);
Firefox Mobile
Current Releases
- Fx for android is now available on the Yandex Store
- Install the Yandex store APK on your Android device to browse and select Firefox for Android http://m.store.yandex.com. As of Tuesday AM, we had 180 downloads and 80 active installs.
- UI Hackathon
- First try of a focused sprint on front-end bugs. This one is focused on UI paper cuts. Current bug list. Starts today and ends on Friday. All are invited to pitch in!
Beta (147)
- We Shipped Beta 3 to GP last week: https://wiki.mozilla.org/QA/Fennec/21/Beta/3
- Qualifying Beta 4 is underway: https://wiki.mozilla.org/QA/Fennec/21/Beta/4
- Ratings average a healthy 4.3 stars
- Record low crash rate still under 3 per 100 adu
Aurora (54)
Nightly (148)
- WebRTC: still behind a build flag but GCP is working steadily on fixes based on his testing as well as other folks who are beginning to contribute feedback, check out his blog post on the topic: Blogged: http://www.morbo.org/2013/04/webrtc-support-on-android.html
- About Home Redesign: is in the "design" phase, good progress is being made not committed to a specific release, yet: https://bug862793.bugzilla.mozilla.org/attachment.cgi?id=739728
- You can now change the default search provider used for quick searches bug 730445
- Domain autocompletion also landed Type Less. Navigate more bug 858340
- Perf Change for Dynamic Nav bar just landed on nightly, please keep an eye open for fallout bug 858969
- A patch is on it's way to fix bug 863803 - LayerView not shown after resuming from an OOM kill
Services
Firefox Health Report
- Continuing on track for Fx21
- Work continues on performance improvements and general resiliency
Product Announcements
- No significant updates this week
Developer Tools
Feedback Summary
Desktop
Mobile
UX & User Research
Market Insights from the Product Marketing Strategy Team
Desktop / Platform
- Now that Google has forked WebKit to create its own browser engine, Blink, work is commencing on many new platform technologies, including animated WebP images, CSS blending for elements and backgrounds, the picture element, vibration API, web MIDI API, object-fit and object-position, equivalents to mozInnerScreenX and Y, a device motion API, lazy-block layout, final portions of the pointer/hover media queries, DOM3 mouse enter and mouse leave events, CSS exclusions, and more. Opera is also contributing code for improved multicol support
Microsoft
- Microsoft unveiled the Your Privacy marketing campaign website, "a new consumer awareness campaign focused on online privacy". The first in a series of television advertisements was posted on their blog.
HTML5
- A developer of HTML5 developer tools crawled the web in search of HTML5 games, and found 1319 of them. His analysis summarized the top game engines, which included Construct2, ImpactJS, and EntityJS.
- JQuery 2.0 was released, dropping support for Internet Explorer 6, 7, and 8.
Marketing, Press & Public Reaction
- Badge Unlocked -- 25 Million Direct Relationships Achieved
The Community Engagement team just past the 25 MILLION mark on the amount of direct relationships established with our user base -- Congrats! That includes anyone who has chosen to follow up through the following means: email, social media, affiliates, and more Having direct relationships is extremely valuable as it gives us a means to speak directly to users - this is absolutely essential when we want to get out the word on new features (like private browsing, below) or launch new products like Firefox OS
- Moved and Improved - Private Browsing Campaign Results
Reminder: We launched a outreach campaign to existing users to help launch our improved Private Browsing changes with the Firefox 20 launch Results: That campaign ended up prompting over 400K users to take action and learn more about these changes, and overall performed within the "average" range, which is expected for very specific feature related communications like this