mozilla.dev.planning Google Group

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

2009-11-23T20:03:06Z

This will be our top agenda item for today's CrashKill meeting.

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

2009-11-23T19:56:43Z

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 20 outstanding blocker nominations:
[link]
Additionally, they should be prepared to discuss the status of all the blockers on this list:

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

2009-11-23T19:53:50Z

They will fail at configure time with `--enable-ipc requires --enable-libxul`
--BDS

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

2009-11-23T19:51:33Z

Hey Benjamin. Sadly, there are a lot of pending landings; as I said in today's meeting, we haven't frozen for Firefox 3.6 yet, and the tree is still restricted until we do. Based on my current estimate, this will have to wait until after the Thanksgiving holiday.
cheers,
mike

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

2009-11-23T19:43:26Z

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)

Top Crash Kill Kill Kill Meeting: Monday, Nov 23 @ 3PM PDT

2009-11-23T19:42:14Z

There will be a meeting, information below, to discuss the killing of crashes, status on current tracked crashes, and tools to help track and find crashes.
General Agenda:
* Status update on identified top crashes.
* Status update on crash tools, tracking, etc.
* Identify tools issues so we can find & fix faster.

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

2009-11-23T19:27:36Z

So what will happen with current mozconfigs that explicitly list
--disable-libxul? Will they just fail to compile unless --disable-ipc
is added? Will they silently do libxul? Keep not doing libxul?
Something else?
-Boris

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

2009-11-23T19:17:49Z

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

Re: An all-green-changeset-only repository

2009-11-23T15:31:36Z

I am going to assert without evidence that we can make improvements
sufficient to make the tree green enough by removing the more frequently
occurring sources of random orange.
IOW, yes, let's cross that bridge when we come to it. If the code does,
in fact, contain hundreds of independent extremely hard-to-trigger bugs

Thunderbird Weekly Status meeting: Tuesday November 24th, 2009

2009-11-23T12:32:29Z

[Followups aimed to mozilla.dev.planning]
The usual meeting in the usual venue. See
[link] for
details, and please add anything you wish to discuss to the agenda.
Standard8

Weekly Status Meeting - November 23, 2009

2009-11-23T06:59:20Z

Meeting Details:
* 11:00am Pacific Standard Time (19:00 UTC)
* Mozilla HQ, 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:weeklysta...@mozilla.com from generic SIP clients
* [link] to watch and listen

Commit Access Policy - draft for comment

2009-11-21T16:17:55Z

[I've had no responses to the below so am currently assuming that it's
all absolutely fine. But just in case it's not, here's a repost
including .planning to try and attract more comment. I wouldn't want
people to feel blindsided. If you know people who might want to comment
on this and you think they won't have seen it, please tell them.]

Re: An all-green-changeset-only repository

2009-11-21T10:04:17Z

Chris Pearce put some information up here:
[link]
[link]
Rob

Re: An all-green-changeset-only repository

2009-11-21T09:54:58Z

I don't think that's completely accurate. We have regression tests
where, if a regression occurs, we expect that the test will fail
intermittently, because we don't know how to write a more reliable test.
I think this is a good distinction, modulo the limitation noted above.
Unfortunately you simply can't do ongoing regression testing without

Re: An all-green-changeset-only repository

2009-11-21T09:41:59Z

Yes, I expect you're right. Someone who remembers more stats than me
(Zack?) can probably work it out under some assumptions.
But suppose we had recording enabled on a set of test machines and over
a long period of time we see a particular failure exactly once. After
the fix, you might need to keep running those machines for an extremely