Difference between revisions of "Status Meetings:2008-01-09:Agenda"

From Camino Wiki
Jump to navigation Jump to search
(→‎Queries: hooray for p!)
(→‎General Plans: oops, extra)
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
* Camino 1.6a1
 
* Camino 1.6a1
 
** [http://talkback-public.mozilla.org/reports/camino/CM16a1/index.html Talkback] ([http://talkback-public.mozilla.org/search/start.jsp?search=1&searchby=stacksig&match=contains&searchfor=&vendor=MozillaOrg&product=Camino16&platform=MacOSX&buildid=2007120712&sdate=&stime=&edate=&etime=&sortby=stack&rlimit=500 all 1.6a1 crashes])
 
** [http://talkback-public.mozilla.org/reports/camino/CM16a1/index.html Talkback] ([http://talkback-public.mozilla.org/search/start.jsp?search=1&searchby=stacksig&match=contains&searchfor=&vendor=MozillaOrg&product=Camino16&platform=MacOSX&buildid=2007120712&sdate=&stime=&edate=&etime=&sortby=stack&rlimit=500 all 1.6a1 crashes])
** Are we getting enough user coverage? Talkback suggests no using the nsCOMPtr_base crashes for a comparison (only 56 crashes total)
+
** Are we getting enough user coverage? Talkback suggests no using the nsCOMPtr_base crashes for a comparison (only 85 crashes total in ca. 1 month)
 
* Camino 1.6b1
 
* Camino 1.6b1
 
** Plan to ship b1 bet. 15th and 17th; freeze when? (relnotes just before freeze, QA during freeze to try to avoid crashers)
 
** Plan to ship b1 bet. 15th and 17th; freeze when? (relnotes just before freeze, QA during freeze to try to avoid crashers)
Line 11: Line 11:
 
** What 10.5 [[#Other (if there's time)|UI integration]] fixes do we want?
 
** What 10.5 [[#Other (if there's time)|UI integration]] fixes do we want?
 
*** Need call for designers to get mockups for 10.5 tab/bookmark bar refresh
 
*** Need call for designers to get mockups for 10.5 tab/bookmark bar refresh
** l10n freeze, so all strings/nib changes must be done by beta; please nominate these
+
** please help out with any nib/strings bugs
** please help out with any P1s (see query below)
 
 
* Camino 1.6
 
* Camino 1.6
 
** [[Development:Planning:Camino 1.6|Scoping]]
 
** [[Development:Planning:Camino 1.6|Scoping]]
 
*** Most of Tab Scrolling is done, as is AppleScript (P3)
 
*** Most of Tab Scrolling is done, as is AppleScript (P3)
*** swupdate: only minor stuff left: Ts regression {{bug|405542}}), appcast script ({{bug|401474}}), '''testing via b1'''
+
***: 2-3 AS follow-ups we really want (peeja)
*** jeff has been poking the tab dragging code; new WIP on {{bug|160720}} with hwaara's comments addressed.
+
*** swupdate: only minor stuff left
*** batwood has patches for both of his 1.6 bugs (multiple accounts needs new patch after r-)
+
***: Ts regression {{bug|405542}}), appcast script ({{bug|401474}}), '''testing via b1'''
*** murph has patches for search editor and OpenSearch (need tweaks and sr); should have a solution to fully establish a working key-view loop throughout the browser window after that
+
*** jeff has been poking the tab dragging code
 +
***: new WIP on {{bug|160720}} with hwaara's comments addressed.
 +
*** batwood has patches for both of his 1.6 bugs
 +
***: multiple accounts up for sr=mento
 +
*** murph should have a solution to fully establish a working key-view loop throughout the browser window after search stuff
 +
***: search editor and OpenSearch have checkin-ready patches
 
*** ardissone has been fighting Makefiles for AppleScript feed handlers
 
*** ardissone has been fighting Makefiles for AppleScript feed handlers
 +
***: needs review=peeja and review/mentoring=mento
 
*** breakpad: mento was going to talk to ted about server-side stuff (and write our handlers); smorgan was going to write the reporter
 
*** breakpad: mento was going to talk to ted about server-side stuff (and write our handlers); smorgan was going to write the reporter
 +
***: updates?
 
* [[Releases:1.5.4:Links|Camino 1.5.4]]
 
* [[Releases:1.5.4:Links|Camino 1.5.4]]
** Next Gecko release scheduled for [http://wiki.mozilla.org/Releases 5 Feb].  We need to push some crash fixes with it (close tabs, quit; Trash button)
+
** Next Gecko release scheduled for [http://wiki.mozilla.org/Releases 5 Feb].  We need to push some crash fixes with it (close tabs, quit; Trash button crashes)
 
** [http://talkback-public.mozilla.org/reports/camino/CM154/index.html Talkback] for 1.5.4
 
** [http://talkback-public.mozilla.org/reports/camino/CM154/index.html Talkback] for 1.5.4
*** topcrasher (#1, #2, and #6) already fixed; it's on quit, but it's pretty heavy
+
*** topcrasher (#1, #2, and #4) already fixed; it's on quit, but it's pretty heavy
 
**** The change that caused it landed on the MOZILLA_1_8_BRANCH one month before we spun 1.5.4 RC build.  Are we not getting enough testing of the branch?
 
**** The change that caused it landed on the MOZILLA_1_8_BRANCH one month before we spun 1.5.4 RC build.  Are we not getting enough testing of the branch?
 
*** Crash on quit ("pass-the-buck" Core {{bug|349463}}) is #3 (bsmedberg has a trunk patch!)
 
*** Crash on quit ("pass-the-buck" Core {{bug|349463}}) is #3 (bsmedberg has a trunk patch!)
*** Flash is #4, #5 (the latter ultimately in Cocoa)  
+
*** Flash is #5, #6 (the latter ultimately in Cocoa)  
 
<!--*** #6 is asstd libSystemB crashes, mostly related to plug-ins (Flash, QT, Divx, F4M)
 
<!--*** #6 is asstd libSystemB crashes, mostly related to plug-ins (Flash, QT, Divx, F4M)
 
*** #7 is a 10.5.1 Flash-related crash, possibly all 1 user
 
*** #7 is a 10.5.1 Flash-related crash, possibly all 1 user
Line 45: Line 51:
 
* Tinderboxen
 
* Tinderboxen
 
** no new news on binus or maya
 
** no new news on binus or maya
** ss has replacement minis for binus (to run 10.3) and mayaTrunk; mini-binus is in the colo but not accessible(?); mini-mayaTrunk will go to the colo after Christmas
+
** ss has replacement minis for binus (to run 10.3) and mayaTrunk; mini-binus is in the colo but not accessible(?); mini-mayaTrunk will go to the colo after Christmas(?)
 
** cb-miniosx01 has Ts disabled due to paging/low installed RAM
 
** cb-miniosx01 has Ts disabled due to paging/low installed RAM
 
** we should think about setting up a testerbox to catch Core bugs breaking embedding APIs (mini-mayaTrunk alternate builds?)
 
** we should think about setting up a testerbox to catch Core bugs breaking embedding APIs (mini-mayaTrunk alternate builds?)
 
* Weekly Bugs and Queues update
 
* Weekly Bugs and Queues update
** Vanishing WIPs
+
** 32 bugs this last week probably a record; heroic effort on the queues, too (only still "high" because we're pushing so many patches in)
 +
** We have lots of bugs where people have said "I have working/WIP code for foo" and never attach patches and then they or the code disappear; we need to get better at attaching WIPs (there are actually several bugs with old Chimera patches we've been able to resurrect because there were patches)
  
 
==Specific bugs that need action==
 
==Specific bugs that need action==
Line 74: Line 81:
 
*** Need to find a way to "promote" this as an area we'd like user feedback on in 1.6a1 (we note this as a feature on the preview site)
 
*** Need to find a way to "promote" this as an area we'd like user feedback on in 1.6a1 (we note this as a feature on the preview site)
 
* '''Trunk'''
 
* '''Trunk'''
** mainly the background drawing/tab-bleeding-on-10.4 bug ({{bug|406784}}) remains
+
** mainly the background drawing/tab-bleeding-on-10.4 bug ({{bug|406784}}) remains (waiting on landing)
 
** Need to keep an eye on trunk regressions, determine if they're Camino-only or partly/wholly Core, and consider requesting blocking1.9? for the latter set.
 
** Need to keep an eye on trunk regressions, determine if they're Camino-only or partly/wholly Core, and consider requesting blocking1.9? for the latter set.
 
** xpfe cleanup
 
** xpfe cleanup

Latest revision as of 10:14, 9 January 2008

Wed 09 Jan 9am PST (17:00 GMT/UTC) in #camino-mtg

General Plans

  • Camino 1.6a1
    • Talkback (all 1.6a1 crashes)
    • Are we getting enough user coverage? Talkback suggests no using the nsCOMPtr_base crashes for a comparison (only 85 crashes total in ca. 1 month)
  • Camino 1.6b1
    • Plan to ship b1 bet. 15th and 17th; freeze when? (relnotes just before freeze, QA during freeze to try to avoid crashers)
    • Feature/l10n freeze is b2
    • What P1/P2 features won't make it?
    • What 10.5 UI integration fixes do we want?
      • Need call for designers to get mockups for 10.5 tab/bookmark bar refresh
    • please help out with any nib/strings bugs
  • Camino 1.6
    • Scoping
      • Most of Tab Scrolling is done, as is AppleScript (P3)
        2-3 AS follow-ups we really want (peeja)
      • swupdate: only minor stuff left
        Ts regression Bug 405542), appcast script (Bug 401474), testing via b1
      • jeff has been poking the tab dragging code
        new WIP on Bug 160720 with hwaara's comments addressed.
      • batwood has patches for both of his 1.6 bugs
        multiple accounts up for sr=mento
      • murph should have a solution to fully establish a working key-view loop throughout the browser window after search stuff
        search editor and OpenSearch have checkin-ready patches
      • ardissone has been fighting Makefiles for AppleScript feed handlers
        needs review=peeja and review/mentoring=mento
      • breakpad: mento was going to talk to ted about server-side stuff (and write our handlers); smorgan was going to write the reporter
        updates?
  • Camino 1.5.4
    • Next Gecko release scheduled for 5 Feb. We need to push some crash fixes with it (close tabs, quit; Trash button crashes)
    • Talkback for 1.5.4
      • topcrasher (#1, #2, and #4) already fixed; it's on quit, but it's pretty heavy
        • The change that caused it landed on the MOZILLA_1_8_BRANCH one month before we spun 1.5.4 RC build. Are we not getting enough testing of the branch?
      • Crash on quit ("pass-the-buck" Core Bug 349463) is #3 (bsmedberg has a trunk patch!)
      • Flash is #5, #6 (the latter ultimately in Cocoa)
    • Still cleaning up stuff from the website switch; file bugs against Product Site if you see anything.
  • Tinderboxen
    • no new news on binus or maya
    • ss has replacement minis for binus (to run 10.3) and mayaTrunk; mini-binus is in the colo but not accessible(?); mini-mayaTrunk will go to the colo after Christmas(?)
    • cb-miniosx01 has Ts disabled due to paging/low installed RAM
    • we should think about setting up a testerbox to catch Core bugs breaking embedding APIs (mini-mayaTrunk alternate builds?)
  • Weekly Bugs and Queues update
    • 32 bugs this last week probably a record; heroic effort on the queues, too (only still "high" because we're pushing so many patches in)
    • We have lots of bugs where people have said "I have working/WIP code for foo" and never attach patches and then they or the code disappear; we need to get better at attaching WIPs (there are actually several bugs with old Chimera patches we've been able to resurrect because there were patches)

Specific bugs that need action

1.6b1pre

  • Bug 408593 - Only check for the default browser once
    • Re-discuss, with mento's objections?
  • Bug 394651 - Set "Accept cookies only from sites I visit" as default (dwitte fixed the Core problem; this can land whenever.)
    • any chance of the NSPR fix needed to enable this landing on the branch, or should we just trunk-only it?

1.5.5

  • nothing right now

Other (if there's time)

  • UNCOs
    • Bug 376930 - Overflow tab menu covers whole upper right part of my screen
      • Need to find a way to "promote" this as an area we'd like user feedback on in 1.6a1 (we note this as a feature on the preview site)
  • Trunk
    • mainly the background drawing/tab-bleeding-on-10.4 bug (Bug 406784) remains (waiting on landing)
    • Need to keep an eye on trunk regressions, determine if they're Camino-only or partly/wholly Core, and consider requesting blocking1.9? for the latter set.
    • xpfe cleanup
      • see older Agendas if you're interested

Queries

Camino 1.6b1

Camino 1.6b2

Camino 1.6

Queues