Firefox:1.5.0.2:Meeting Notes

From MozillaWiki
Jump to: navigation, search

Notes about these notes

  • Firefox 1.5.0.2 discussions of non-security-sensitive bugs are recorded on this page
    • Discussions regarding security-sensitive bugs are recorded on the internal security wiki
    • see http://www.mozilla.org/projects/security/ for public information about security issues
    • This page is not a channel to request or announce information about specific security-sensitive bugs
  • Updates to this page should come from attendees of the Firefox 1.5.0.2 meetings
  • If you disagree with the decision of the triage committee about a specific bug, please present your case in the comments for that bug

Release Team Members

The Release Team is run by:

  • Dan Veditz - Co-lead/Dev
  • Tim Riley - Co-Lead/QA
  • Dave Liebreich - QA Lead
  • Paul Reed - Build

Occasional Attendees:

  • Axel Hecht - L10n
  • Rafael - Marketing
  • Bob Clary - JS/Security QA

All are welcome to attend!

These meetings are:

  • Mon,Wed, Thurs, Fri - 11am PST
  • Tues - 2pm PST

See IRC Channel #1502

Dial-in:

  Toll-free Number:      866-432-7917
  International Number:  334-309-0297

Notes

(2006-02-06) Pre-meeting Bug Stats

(2006-02-07) Triage meeting

(2006-02-08) Triage meeting

(2006-02-09) Triage meeting

(2006-02-27) Update

  • I apologize for not keeping these notes up to date
  • I'm going through the Firefox bugs marked fixed1.8.0.2 and adding pseudo-flags to the status whiteboard in the format [xxx-dl]
    • [rft-dl] - ready for testing - ready for qa to verify the fix
    • [tcn-dl] - test case needed - need more info to verify the fix
    • [tjp-dl] - test japan - need to ask mozilla japan folks to help verify
    • [nvn-dl] - no verification needed - I think we can skip directed/focused verification of this bug. Usually because:
      • this is an internal architecture change and we're just looking for anything else that breaks
      • this fixes a topcrasher, and we'll look at the topcrash stats after release to make sure the crash frequency goes down
      • build/packaging issue (like building univeral binaries for macos, or BeOS-only changes) - if the builds exist and run, the patch is ok
      • covered by testing we do anyway. Some software update changes are covered by this flag
  • As always, let me and/or drivers know if you disagree with a flag. I'm very willing to change my mind when presented with new information.
  • Our goal is to verify all critical security fixes, and 60% of all fixes overall, before releasing 1.5.0.2

(2006-03-06) Update

  • What is the priority of MacIntel bugs?
  • What is priority between Builds bugs and Universal build setup
  • Blocking/Needs Landing bugs:
    • 327014 - Get Boris, dbaron, or joahas to land?
    • 328981/328982 - need new reviewers
    • Need 329406 to start Win BFTs - final bits for release candidate

(2006-03-08) Update

  • Don't have tinderboxes for Universal binaries - blocker bug
  • Number of bugs for Universal binary
    • Is this ready to go?
  • Build
    • Need Linux build - nightly broken
  • Held up on Mac builds due to - Universal binary issue.
    • Tim to check with Schrep and mktg

(2006-03-09) Update

  • Dave wants JA build for Ja team testing
    • To test core fixes for JA
    • Win only, JA-jp
  • Mac Universal Binaries (UB)
    • Smoke test on MacPPC - Done
    • When UB is done, we will do some minor retesting of PPC.
    • Dave is posting an outline of what PPV and Intel Mac testing should be done. This will be in the test plan?
  • Verifications
    • At this point 97 fixes verified - 10 more TBD by Ja
      • Goal is 104 fixes verified
    • Some Critical security bugs still need to be tested
      • Less than 11
      • Some of these can only be verified by code inspection. See the "no verification needed" flag - "nvn-dl" in the status white board.
      • Others will be verified by by Bob's Security Test Library tests
  • Testing remaining before "Go" for tagging/signing and setting date for Community Test day:
    • Ext test - top 10/Recommended/Ext winners
    • Run Security Test Library on one plaform - Dave to check with Bob to see if this was done
    • Plan to set date for Community Test Day tomorrow.
  • TB testing?
    • Smoke on all platforms
    • BFT on Win
    • Marcia will work with Scott to plan TB testing
    • What % of bugs to verif for TB?
    • What about UB for TB?
  • Resolving UB issues
    • Why core bugs need to be fixed?
    • How is Camino relelasing UB
    • Why no official build for UB if released for Camino
    • Get Josh in Release Team tomorrow - Marcia

(2006-03-10) Update

  • No pending approval requests
  • UB
    • basic set of tests on PPS and Intel
    • testing
      • profiles from PPC -> Intel [Josh]
      • Check anything that writes out files - Address book
      • no other known problems [josh]
      • Same SDK for Intel?
    • Builds off of Maya
    • Tinderbox setup by Josh and
    • No talkback
    • Build Issues:
      • 327092
      • Tinderbox available early next week
      • Josh to check into bug 329801 - Mark cutting patch to this.
      • Builds ~ Wed/Thursday next week <<== AI: Preed
    • Concern about updates with UB
      • non-UB to UB updates - build side
      • Applying patch to client
      • Server side - platform URL - new platform type on the server
      • Update not tested at all!!
    • What happens if UB update a huge problem? [mscott]
      • Ship A PPC Mac only and the either:
        • Provide only full install for UB or..
        • Delay UB release
      • What about TB UB?
        • Preed they would go on same tinderbox so also due next week
  • TB Testing Plans:
    • BFT on Win
    • How many fixes to verify <<== AI: Marcia/Tim
    • Extended smoketest on all platforms
    • Community testing? [davel]
      • posted to forum, etc, but community not interested [mscott]
      • Combine TB abd FF test date
        • At least put info about TB in QA blog about FF test day.
        • Leverage Tomcat for TB testing!?
  • QA
    • BC completed STL test for win, JS for All platforms
    • Completed Ext testing - Top 10, Ext contest winners
    • BTF on win - Done
    • Smoketests on Lin/Mac - Done
    • "Go" for tagging/signing <<== Decision
      • Preed can start tagging/signing at any time
    • 60% and Critical/Sec fix verification done!
  • Build
    • Is this RC1 or just a regular release candidaite?
    • Reg relelase candidiate - we want commnity testing for UB (eventually) and exit survey <<== Decision
    • Need to finish 1.0.8 and then start 1.5.0.2 next week. Let's wait for UB for RC1 <<== Decision
  • JA build for Dave to give to Ja team to test jp-critical bugs?
    • [Preed] Ping coop for a build <<== AI: Dave/Coop

  • Need to look into brand new Blocker Nomination: 330044 and related bug:
    • 320349 (Darin Non-blocker approval request)
    • AI: Dan and Scott to look into bugs and check with Darin

(2006-03-13) Update

  • Ja build for testing key fixes by the Ja team: behind Universal Builds (UB). Stay tuned.
  • UB Builds: patch to Tinderbox before setting up UB. Mark will get back to Preed. Hopefully this will be setup today.
  • Withing 2 bugs of 60% of verfication target
  • Good to go for "Go" to tagging/signing
    • move build to candidates directory <<== AI: Preed
    • Start pulling by date? [mscott] <<== AI Preed
    • Send Preed the version IDs <<== AI: Marcia
    • Use 3/7 and 3/8 builds
  • Create update channel? [davel]
    • Proposal: setup Beta channel for release candidiate
    • Check into effort for this
  • Which version to use for TB?
    • Use the same version from FF for TB: 3/7/06, 3/8/06 <<== Decision
    • Smoke tests on all platforms
    • use PPC Mac
    • BFT on Win
    • Ext testing
    • Fix verifications
      • 327 - 1.5.0.1, 1.5.0.2 bugs fixed for TB
      • mscott to provide list of key bugs to verif for TB
      • Need keyword/whiteboard flag
        • Why: to not duplicate verif, to monitor status
        • Use whiteboard: [qa:verified-TB-1802]
  • Exit survey - client side works ok!
    • See bug 325042 - relnote?
    • Need to setup service side - there is a bug number

(2006-03-14) Update

  • Update on Universal Binary (UB) for MacOS - Preed is still working on it.
  • What level of verification do we want to do for TB?
    • Keyword for [qa:verified-tb-1802] <<<=== AI: TR to publish
    • Scott's list
    • Security bugs
    • Critical bugs
    • Monitor each day - In triage meeting
  • TB Testing - deep into smoke tests
    • DnD supposed to work for RSS feeds did work - not now
    • Problems with web page as attachement - still investigating
  • Exit survey usability issue
  • Resend release checklist to Rafael <<<=== AI: Tim

(2006-03-15) - no discussion

(2006-03-16) Update

  • Build ids for 1.5.0.2 Marcia -> Preed <<== AI: Marcia
  • Need Ja build from Preed - still on queue; low priority
  • Exit survey - just need server side thing done
    • Issue with IE - davel raised the issue
    • Bug # for IE issue? <<== see Darin's bug - Don't Fix - davel to nominate for 1.5.0.3 <<== AI: Davel
    • Bugs for server side: bug 325042 and bug 322884
  • Universal Binary (UB) for MacOS
    • Being built and tested by tinderbox - passes these steps
    • Problem being delivered to FTP server
    • Should be up on ftp site tonight or tomorrow morning
    • Need commnity testing (with intel macs!) to test migration of profiles, address book. <<== AI for test day!
  • L10n for FF
    • builds will be done in the next few days
  • Discussed bug 327140 - generating partial updated for mac builds. Didn't capture the details of the discussion.
  • Status of TB testing
    • Win BFT started
    • Win/Mac/Linux - smoketest - done
      • Linux - some additional testing needed
    • Fix verifications started
  • Build Tagging
    • Preed is going to do a clean tagging of 1.0.8, 1.7.13, 1.5.0.2
      • What is specific date to use for tag? <<== AI: Marcia
      • Complete by end of tomorrow
  • Seamonkey bug 328932 from Neil
    • "Proposed Patch" javaconsole - no too late - can make their own change - this
    • "toolkit patch" Ok if seamonkey only code and no need to re-build FF/TB
    • Tim to update bugs and notify Neil <<== AI: Tim
  • Review schedule updated schedule: http://wiki.mozilla.org/Firefox:1.0.8:Schedule
    • Concerned about 3 day on-site event that is not reflected in the Build schedule.
    • Do we really know how to release 3 versions for 2 products and 30 something locales on one day!!!
      • Marcia will sketch out QA activities and come back to us.
      • Releasing TB a week later would be ok form a security standpoint

Links into later meeting notes