Firefox 3.6.2 / 3.5.9 / 3.0.19 now code frozen

Hey everyone, We are now code frozen on Firefox 3.6.2 / 3.5.9 / 3.0.19 (which align to = Gecko 1.9.2.2 / 1.9.1.9 / 1.9.0.19 respectively). This means that = patches (except for test and "not part of the build" changes) are no = longer allowed on those trees - all patches marked with the relevant = approvals have either landed or had those approvals revoked. The branch driving team recognizes that there is still a large list of = approval1.9.2.2 nominations - we will continue to work through that = list, moving nominations to approval1.9.2.3 if they are likely to be = taken, or ind

no administrator here to delete the repulsive spam ?

eof

Reminder to use mochi.test in your mochitests instead of localhost

Today we changed mochitests to use "mochi.test", 127.0.0.1, or example.com in place of "localhost". This is to enable getting mochitest to run on windows mobile as outlined in more detail here: * <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=544097">bug 544097</a> * http://elvis314.wordpress.com/2010/02/26/more-info-on-the-localhost-mochi-test-change/ If you have any questions, feel free to comment in the bug, on my blog or just find me (:jmaher) on irc. Thanks, Joel

Next 1.9.3 alpha (this week?)

I'd like to schedule the next 1.9.3 alpha for later this week, with the following focus: * Windows D2D support: fix a bunch of issues (Still preffed off by default) * OOPP: asynchronous stream delivery and topcrash/hang issues Are there any other upcoming features that would fit in an alpha this week? (Code-freeze midnight Thurdsay)? I'd like to push this alpha as a minor update for existing users and have it available for D2D testing as part of a regular biweekly alpha cycle on trunk. --BDS

No CrashKill Today

All, No CrashKill meeting today. If you have agenda items that need = attention right now (I polled people directly for today, no items, but I = can't cover everyone) or have items for next week, please send them to = me. Cheers, Damon

pthc, bbs pthc, pthc board

// // // Robert, look at this, tube site with prete**ns http://doiop.com/secretvids // // pthc bbs pthc pthc board pthc bbs pthc cp pthc links japanese pthc pthc bbs message board cp pthc pthc gallery pthc bbs gallery bbs loli pthc pthc pics free pthc bbs pthc forum lolita pthc pthc sex pthc guestbook pthc lolita pthc mclt video porn clips zeps guide pthc cp pthc preteen pthc vicky pthc pthc torrent pthc vicky pthc board post lolita bbs pthc pedo pthc pthc r(at)ygold pthc tgp

Lorentz coordination meeting: 3-March-2010

The Lorentz coordination meetings continue today: Summary: * Known issues to fix before beta * Crash and bug report monitoring from 1.9.3a2 * Crash report UI/privacy policy summary * Backporting to 1.9.2 Details: * Agenda: https://wiki.mozilla.org/Electrolysis/Meetings/2010-03-03 * Wed 3-Mar @ 1PM PST * 650-903-0800 x92 conf #8605 (US/INTL) * 1-800-707-2533 (pin 369) conf #8605 (US) * irc.mozilla.org #planning for backchannel

Mozilla Developer Preview (Gecko 1.9.3a2) available for download

A Mozilla Developer Preview is now available for download. This is the second pre-release version of the Gecko 1.9.3 platform, which forms the core of Firefox and other Mozilla projects. Out-of-Process Plugins The main feature of this release is out-of-process plugins: on Windows and Linux, plugins such as Flash and Silverlight run in a separate process from the browser. If a plugin crashes it will not crash the browser, and unresponsive plugins are automatically restarted. (Note that we are working on this for Macs as well, but is not part of this preview release.) We are

Firefox / Gecko Development Meeting: Tue Mar 2 @ 11am PST

The next Firefox/Gecko Development Meeting will be Tuesday at 11am PST. = See below for meeting time, location, and agenda: General Agenda: * Development schedule for branch work. * Gecko 1.9.3 Alpha 3 status and plan. * Updates on Out of Process Plugins, E10s, J=E4gerMonkey, Layers, D2/3D, = and other projects. Meeting Details: * Agenda: https://wiki.mozilla.org/Platform/2010-03-02 * Tue, Mar 2, 11:00 am PST * 650-903-0800 x92 Conf# 8605 (US/INTL) * 1-800-707-2533 (pin 369) Conf# 8605 (US) * join irc.mozilla.org #planning for back channel Sincerely, Damon

Linux 64 debug builds

Hi all! We have enabled linux 64 debug builds on all branches. The first run will fail because there were no previous leak, bloat and sdleak logs on ftp. I am triggering a double run for each builder. Debug builds FTW! Let me know if you find any problems on the bug or through IRC channels (armenzg on #build and #developers) For more information: Bug 512489 - officially support Linux x86-64 builds

Re: Posting Method Stats

With this, I begin to question the mechanism by which you're collecting your stats - or does Hendrix post by way of NNTP? cheers, mike ----- Original Message ----- From: dev-planning-bounces+beltzner=mozilla.com@lists.mozilla.org <dev-planning-bounces+beltzner=mozilla.com@lists.mozilla.org> To: dev-planning@lists.mozilla.org <dev-planning@lists.mozilla.org> Sent: Fri Feb 26 04:42:28 2010 Subject: Re: Posting Method Stats Justin Wood (Callek) wrote on 25. Feb 2010: >> Total Google Mail News >> mozilla.dev.apps.seamonkey.mbox >> Posters: 213

scheduled downtime - 5AM-8AM PST (Thursday 25th)

Production master 2 is in a weird state and the only way to fix it is to restart it. The downtime will restart the master and I will retrigger nightly builds and dependent builds for aborted builds. Therefore, everyone should be getting their builds just later than usual. No need to close the tree. The downtime will be from 5AM PST to 8AM PST. The branches affected are: * tracemonkey * 1.9.1 * electrolysis * lorentz * all mobile builds For more details check bug 548467. Sorry for any inconveniences. Please let me know if this downtime should not happen.

Delivery Meeting, Feb 17 at 11am PT

Hey everyone, Sorry for the late notice. Our weekly product delivery meeting will take = place today, Feb 17 at 11am PST. Agenda, notes and dial in information here: = https://wiki.mozilla.org/Firefox/DeliveryMeetings/2010-02-24 Main topics include: * upcoming security branch releases * update on mozilla-central, Fennec and Lorentz projects * updates from Marketing on browser choice! Details # Mozilla Mountain View (Square Room) # 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL) # 1-800-707-2533 (pin 369) Conf# 8605 (US) # irc.mozilla.org #planning for backchann

1.9.3alpha2 soon

We are planning to do another alpha release of 1.9.3 this week with out-of-process plugins on by default. The following bugs should be resolved today or early tomorrow: * bug 532208 - make browser->plugin streams unidirectional * bug 545734 - hide the iframe used to submit plugin crash reports * bug 547894 - topcrash with DivX passing null to a string function * bug 544074 - topcrash at PluginModuleChild::UnregisterActorForNPObject The only other bug which I know needs to block the current alpha is bug 545195, a mysterious topcrash on shutdown. bent is investigating, trying to

Linux 64 and puppet

We are going to add puppet to the linux 64 production slaves during this week. This should not require any downtime and should be invisible for everyone (no reds/burns). This is only for build slaves and it has nothing to do with talos machine changes. To follow up on this check out https://bugzilla.mozilla.org/show_bug.cgi?id=505232

Weekly UX meeting: Agenda

Today's UX meeting is at 13:30 PST, and has the following agenda: 1. Overview of what was done during the (short) last week 2. Update the Firefox Projects<https://wiki.mozilla.org/Firefox/Projects>list 3. Plans for the Work Week, who should we schedule to meet with, what activities should we prioritize, etc. 4. Plans for the current week You can call in to conference room 268 (dial-in numbers here<https://wiki.mozilla.org/Firefox/DeliveryMeetings/2010-02-17>) every Monday at 13:30 PST. (I'm working from home today due to a sore throat, so will be calling in too)

Weekly reminder - please add your updates to the Wiki for Monday!

Hi everyone, Please add your weekly updates to the wiki page at https://wiki.mozilla.org/WeeklyUpdates/2010-02-22 before 10am PST Monday. You know the drill by now: If you want to speak, add yourself to the Speakers section; if you've got an event, add it to the Upcoming Events section; and if it's a general progress update, add it to the appropriate team status section. Thank you very much! See you Monday! --Jono

No Weekly Status Meeting - January 18, 2010

It is a holiday in the United States today, and so the regular weekly = status meeting will not be held. Apologies for late notice. Contributors = are encouraged to place their updates in the wiki as notes, and these = will be published to Planet Mozilla: https://wiki.mozilla.org/WeeklyUpdates/2010-01-18 (sorry for the late notice) cheers, mike=

AUTO: Hirsch, Julie is out of the office. (returning 01/18/2010)

I am out of the office until 01/18/2010. I am out of the office on Friday, January 15. Will return to on Monday, January 18. If you are a Humana Associate and need immediate assistance, please call CSS at extension 2700. If this is an emergency, please contact my manager Glenn Morgan or call 502-476-3333 to leave a message in the ATS on-call voicemail. Note: This is an automated response to your message "Firefox 3.6 Release Candidate 2 is available for download" sent on 1/17/10 18:15:20. This is the only notification you will receive while this person is away. T

Testday: Website Compatability with Firefox 3.6 - Friday January 22nd

The MozQA community is holding a Testday on Friday, January 22nd, for anyone interested in the performance, look and feel, stability, and general usage of their favourite websites with Firefox 3.6! It will be a day filled with testing various websites, sites you use day to day, with the bleeding edge release of Firefox 3.6. The community will be hanging out online doing testing all day via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you're interested, come on by anytime between 7AM to 5PM PDT that Friday! For more information, please go to http://quality.mozilla.or

Thunderbird 3.0.1 beta available for testing

Candidate builds of Thunderbird 3.0.1 are now available for testing. Note: these are intended for pre-release testing and are not recommended for production use. Download You can get the Thunderbird 3.0.1 builds here: ftp://ftp.mozilla.org/pub/thunderbird/nightly/3.0.1-candidates/build1/ Update If you have previously downloaded a beta version of Thunderbird 3 or have manually set your copy to be using the "beta" release channel for updates, you can update yourself to Thunderbird 3.0.1 by selecting "Help > Check for Updates". Feedback and Bugs If you see any issues with

Fwd: Removal of the Profile Manager UI?

Accidentally posted it only to mozilla.dev.planning. -------- Original Message -------- Subject: Removal of the Profile Manager UI? Date: Tue, 12 Jan 2010 23:09:09 +0100 From: Henrik Skupin <hskupin@gmail.com> Newsgroups: mozilla.dev.planning While checking bug mail today I have seen a comment from Benjamin Smedberg on bug 278860 (https://bugzilla.mozilla.org/show_bug.cgi?id=278860) which is about the confusing profile manager warning when a profile is already in use. I was really upset when reading his statement in comment 91: > In any case, I'm > trying to remove the profil

Fwd: 3.1a1 string & code freeze Tuesday, Jan 12 at 23:59 Pacific, perhaps

This is a multi-part message in MIME format. --------------060409010308060309000100 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit [Reposted due to gatewaying issues with the original message sent yesterday] [Mailed to various lists; followups directed at dev-apps-thunderbird] Our development schedule has today (Tuesday, Jan 12, at 23:59 Pacific) marked as when we go into string & code freeze for Thunderbird 3.1 (Lanakai) Alpha 1 (see <https://wiki.mozilla.org/Thunderbird:Thunderbird3.1> for more detail). Sadly, I've had my atte

Socorro 1.4 release planning - feedback welcome

Socorro 1.3 released last Thursday. Our current plan for 1.4 has the following high priority bugs #1) Support Electrolysis work https://bugzilla.mozilla.org/show_bug.cgi?id=535829 - Collect/report additional metadata for out-of-process plugins #2) Integrate dbaron's correlation reports https://bugzilla.mozilla.org/show_bug.cgi?id=525785 - Integrate correlation reports into Socorro UI #3) Prepare for future Hadoop system https://bugzilla.mozilla.org/show_bug.cgi?id=538206 - Add code to crash-report web heads to emit raw crash data to Hadoop cluster in addition to NFS As well

No CrashKill Meeting Today

All, After checking with most of the interested parties, it seems we're in a = holding pattern, watching for new crashes and issues with the RC. No = CrashKill meeting today.=20 In the meantime, if you want to watch for new crashes, check out = http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.6=20 Sincerely, Damon

Mobile Firefox RC Testday Tomorrow!

We're holding a testday on Mobile Firefox RC tomorrow from 7AM - 5PM PDT for the latest RC of Mobile Firefox 1.0 on Maemo Devices! If you don't have a Maemo-based device, you can also download desktop builds for the latest release. For a list of things we anticipate doing tomorrow, take a look at the following link: https://wiki.mozilla.org/QA/Fennec#Testing_Strategy To download the latest build for your platform, you can go over to https://www.mozilla.com/en-US/mobile/1.0/releasenotes/ for the newest release candidate build. For more information, here's our event details page: http

Firefox 3.6 Release Candidate builds started

Hey everyone, Just wanted to follow up to let everyone know that after months of = development, we've started builds for Firefox 3.6 Release Candidate = builds. We're pretty excited. This is the point where people start asking me about "oh, but what about = this patch that didn't make it in?" That's a fine thing to ask, and soon = enough I'll be filing bugs to get new flags created for the inevitable = Firefox 3.6.1. In the meantime, if there's a patch you want considered = for the dreaded status of "RC ridealong," please do so by sending me or = another driver private email. Be s

Firefox / Gecko Development Meeting: Tue Jan 5 @ 11am PST

The next Firefox/Gecko Development Meeting will be Tuesday at 11am PST. = See below for meeting time, location, and agenda: General Agenda: * Development schedule for branch work. * Blocker review for RC. * Nomination review for RC. Meeting Details: * Agenda: https://wiki.mozilla.org/Platform/2010-01-05 * Tue, Jan 5, 11:00 am PST * 650-903-0800 x92 Conf# 8605 (US/INTL) * 1-800-707-2533 (pin 369) Conf# 8605 (US) * join irc.mozilla.org #planning for back channel Sincerely, Damon

Re: Firefox "Lorentz" and 1.9.2/1.9.3

I think this discussion has meandered quite far off the topic of the original request for input that Benjamin wrote. If we want to discuss the various mechanisms and metrics for code quality and maturity separately, I suggest a newsgroup other than dev.planning - perhaps dev.platform? cheers, mike ----- Original Message ----- From: dev-planning-bounces+beltzner=mozilla.com@lists.mozilla.org <dev-planning-bounces+beltzner=mozilla.com@lists.mozilla.org> To: dev-planning@lists.mozilla.org <dev-planning@lists.mozilla.org> Sent: Sat Jan 02 10:58:31 2010 Subject: Re: Firefox "L

Recalibrating Talos performance results on newer hardware

If you don't care about Talos performance results, or Talos hardware, stop reading now! In the last dev platform meeting, I mentioned we'd be doing a lot of Talos recalibration work in early January 2010, and promised updates as we figured out the plan. We're still working out some details, but here's what we know so far. Talos runs performance tests on mac mini hardware. The 1.83GHz minis we use today were all spec'd 2+ years ago, when we migrated from the previous 1.66GHz minis. During 2009, we kept buying and powering up more 1.83GHz minis to keep up with increasing demand of

Firefox 3.5.7 beta available for testing

Once again, warm greetings to all of our great community testers - you are our most valuable resource. We now have a Firefox 3.5.7 release candidate available for testing. Note that this builds are release candidates and is intended for pre-release testing. We would like your help in testing the release candidate sand identifying any possible regressions or issues. *What to Test/Where to Get Builds**:* (Note: If you are riding the "beta" channel, you can manually check for updates and update to this build). Otherwise you will have to download from the directory below.

Firefox / Gecko Development Meeting: Tue Dec 22 @ 11am PST

The next Firefox/Gecko Development Meeting will be today at 11am PST. = See below for meeting time, location, and agenda: General Agenda: * development schedule for branch work * blocker review for RC * nomination review for RC * holiday coverage * quick overview and status updates, not expecting much here :) Meeting Details: * Agenda: https://wiki.mozilla.org/Platform/2009-12-22 * Tue, Dec 22, 11:00 am PST * 650-903-0800 x92 Conf# 8605 (US/INTL) * 1-800-707-2533 (pin 369) Conf# 8605 (US) * join irc.mozilla.org #planning for back channel cheers, mike=

automated test policy for mail/, mailnews/, editor/, directory/ in comm-central

[Note that replies are redirected to dev-apps-thunderbird] As mentioned in previous post-Tb3 planning discussion centered around <https://wiki.mozilla.org/User:Dmose/Tb_Post-3.0_Scratchpad#Testing>, I believe Thunderbird needs to become significantly more agile by bringing our testing polices in line with those of the browser/ and toolkit/ directory in mozilla-central. Which is to say that I'd like to start requiring that all patches to mail/, mailnews/, directory/, and editor/ include automated tests starting Monday, January 4, 2010, except in cases where it's specifically

Mozilla RelEng Scheduled Downtime - Friday December 18, 2009 at 9:00pm PST (~2 hours)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The RelEng team needs to restart the buildbot master on production-master02 to pick up some missing schedulers (see bug 534953). It's not the most complicated procedure and this can generally be done in a matter of minutes, but load on these masters is pretty high so I'm budgeting 2 hours to be safe. Any builds in progress will be lost, but I've chosen this particular time to ensure that the restart happens *before* any nightlies are triggered. Affected products/projects/branches: * 3.5.x release builds * mobile release builds *

Firefox 3.5.6 and 3.0.16 now available for download

As part of Mozilla's ongoing security and stability update process, Firefox 3.5.6 and Firefox 3.0.16 are now available for Windows, Mac, and Linux for free download: Firefox 3.5.6: http://www.mozilla.com/firefox/ Firefox 3.0.16: http://www.mozilla.com/firefox/all-older.html We strongly recommend that all Firefox users upgrade to these releases. If you already have Firefox, you will receive an automated update notification within 24 to 48 hours. You can also manually fetch this update by selecting "Check for Updates..." from the Help menu. For a list of changes and more info

Making unexpected assertions turn the tree orange (for reftest/crashtest/jsreftest)

[ Cross-posted to dev-planning and dev-tree-management. Please follow up to dev-tree-management. ] A while back, I added code to the reftest harness to report test failures for unexpected assertions. I'm planning to turn this on on mozilla-central in the next week or two. This will significantly expand our test coverage for assertion failures, which are currently tested for only on the very simple leak test that the "L" builds do, and, I think, in C++ unit tests and xpcshell tests. This will help us catch regressions that cause new assertions, which are both annoying in thems

Weekly Status Meeting - December 14, 2009

Meeting Details: * 11:00am Pacific Standard Time (19:00 UTC) * Mozilla HQ, Ten Forward area * +1 650 903 0800 x92 Conf# 8600 (US/International) * +1 416 848 3114 x92 Conf# 8600 (Canada) * +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free) * sip:weeklystatus@mozilla.com from generic SIP clients * http://air.mozilla.com/ to watch and listen * join irc.mozilla.org #staffmeeting for backchannel Add your agenda items/status here prior to the meeting: https://wiki.mozilla.org/WeeklyUpdates/2009-12-14 --Tim

RESOLVED: ITTOOKUSTOOLONG

Sorry if this is not quite the right venue, I forgot where the mozilla-bugzilla issues are discussed. The RESOLVED category is missing a very important case: a category for bug reports that were not evaluated in a timely manner. Apparently these get dumped into RESOLVED: INCOMPLETE, which described: The bug is vaguely described with little to no steps to reproduce. http://quality.mozilla.org/bugs-life-walkthrough#resolved This is yet another let's-insult-the-user category and anyway does not fit the "bug report filed against FF 2" category. Ok the bug was not important

No Delivery Meeting December 9th, 2009

Most stakeholders will be busy with other meetings this week, so no meeting. I'll post to this newsgroup and update the notes on the wiki with status report. cheers, mike

No Gecko/Firefox Dev Mtg Dec 7, 2009

All, There will be no Gecko/Firefox Dev meeting this week. Will resume next week. Cheers, Damon

Product Delivery Meeting today at 11am PST

Hey everyone, Our weekly product delivery meeting will take place Dec 2 at 11am PST. This meeting will discuss: * upcoming product releases * report from Support, QA, Localization, Add-Ons, Partners, Evangelism, = PR, and Marketing Agenda, notes and dial in information here: = https://wiki.mozilla.org/Firefox/DeliveryMeetings/2009-12-02 Details # Mozilla Mountain View (Square Room) # 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL) # 1-800-707-2533 (pin 369) Conf# 8605 (US) # irc.mozilla.org #planning for backchannel cheers, mike=

Tests with JIT disabled?

I'm wondering if the Firefox tests are run with JIT enabled always? I guess that Firebug somehow causes the JIT not to be running, so code running while Firebug is active will be less tested than normal path code unless the Firefox tests are run with JIT disabled as well as enabled. jjb

Firefox / Gecko Development Meeting: Tue December 1 @ 11AM PST

The next Firefox/Gecko Development Meeting will be Tuesday at 11am PST. = See below for meeting time, location, and agenda. Echoing Beltzner's request from before: In preparation for this meeting, all team leads and drivers should look = through this list and ensure that they've made blocking decisions on the = outstanding blocker nominations: = https://bugzilla.mozilla.org/buglist.cgi?quicksearch=3DALL%20flag%3Ablocki= ng-firefox3.6%3F%2Cblocking1.9.2%3F Additionally, they should be prepared to discuss the status of all the = blockers on this list: = https://bugzilla.moz

Weekly Status Meeting - November 30, 2009

Meeting Details: * 11:00am Pacific Standard Time (19:00 UTC) * Mozilla HQ, Ten Forward commons area * +1 650 903 0800 x92 Conf# 8600 (US/International) * +1 416 848 3114 x92 Conf# 8600 (Canada) * +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free) * sip:weeklystatus@mozilla.com from generic SIP clients * http://air.mozilla.com/ to watch and listen * join irc.mozilla.org #staffmeeting for backchannel Add your agenda items/status here prior to the meeting: https://wiki.mozilla.org/WeeklyUpdates/2009-11-30 --Tim

Breitling Windrider Headwind Steel Black Mens Watch A453551-B5-350A

Breitling Windrider Headwind Steel Black Mens Watch A453551-B5-350A http://www.watchestrade.net/Breitling-Windrider.html http://www.watchestrade.net/Breitling-Watches.html http://www.watchestrade.net/Breitling-Windrider-Headwind-Steel-Black-Mens-Watch-A453551-B5-350A.html http://www.watchestrade.net/ <br />Stainless steel case and bracelet. Black dial. Date displays at 3 o'clock position. Day displays at 12 o'clock position. Unidirectional rotating ratcheted bezel. Cambered sapphire crystal, glareproofed both sides. Screw-locked crown with two gaskets. Deployment cla

TechnoMarine Technosquare Chronograph Magnum Men's Watch TSCMA11

TechnoMarine Technosquare Chronograph Magnum Men's Watch TSCMA11 http://www.watchestrade.net/Technomarine-TMC.html http://www.watchestrade.net/Technomarine-Watches.html http://www.watchestrade.net/TechnoMarine-Technosquare-Chronograph-Magnum-Mens-Watch-TSCMA11.html http://www.watchestrade.net/ <br />Availability: Usually Ships In 1 - 2 Business Days TechnoMarine Technosquare Chronograph Magnum Men's Watch TSCMA11 This TechnoMarine Technosquare Chronograph Magnum Men's Watch TSCMA11 watch case is made out of Stainless steel. The Silver dial is covered in Sapphire. The

Product Delivery Meeting today at 11am PST

Hey everyone, Our weekly product delivery meeting will take place Nov 25 at 11am PST. This meeting will discuss: * upcoming product releases * how shipping decision for Firefox 3.6 will be made * report from Support, QA, Localization, Add-Ons, Partners, Evangelism, PR, and Marketing Agenda, notes and dial in information here: https://wiki.mozilla.org/Firefox/DeliveryMeetings/2009-11-25 Details # Mozilla Mountain View (Square Room) # 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL) # 1-800-707-2533 (pin 369) Conf# 8605 (US) # irc.mozilla.org #planning for backchannel

Re: Idea for getting a better total crashes per day baseline

I've proposed this idea before, and believe that I even filed a bug on it, but generally agree that the time to submit data about stability is when we specifically ask users if they want to send us that data (ie: the crash reporter). There are several pieces of data we can send along with a crash that are not personally identifiable (though some are what's considered potentially personally identifiable): - time since last crash - total number of crashes experienced - total number of crashes experienced in last 10 minutes, hour, 12 hours and 24 hours - crash report UUID

Firefox / Gecko Development Meeting: Tue November 24 @ 11AM PST

The next Firefox/Gecko Development Meeting will be Tuesday at 11am PST. = See below for meeting time, location, and agenda. General Agenda: * Planning for the next release of 1.9.2 * discuss upcoming major changes landing on mozilla-central * Status updates on feature development (both front-end and platform) * Identifying areas of code risk for upcoming milestones * Discussion of security review impacts, standards/spec compliance work, internal and external dependencies Meeting Details: * Agenda: https://wiki.mozilla.org/Platform/2009-11-24 * Tue, Nov 24, 11:00 am PST * 650-9

Landing multi-process plugins in mozilla-central (Tuesday)

The electrolysis tree is completely green and we think we've resolved all the remaining code blockers to land out-of-process plugins (OOPP) into mozilla-central. Unless I will be interfering with Firefox 3.6/1.9.2 work, I'd like to do this tomorrow morning (Tuesday). This means the tree will probably be closed/restricted for at least a couple hours. Please let me know if there are pending landings for 3.6 which would be delayed by closing mozilla-central tomorrow morning. * Because the electrolysis branch contains both plugin and tab work, this will not be a straight up merge from e1