gmane.comp.mozilla.devel.seamonkey

Gaia Triage

Dietrich Ayala — 2012-05-26T00:06:02

Weekly on Thursday at 0800 PDT / 1700 CET / 2300 CST
Vidyo: Dietrich's room (until we get the B2G room set up)

https://etherpad.mozilla.org/gaia-triage

This week we'll cover the unclassified bugs, then pass through
QA-blocked and platform-blocked.

B2G Platform Triage

Dietrich Ayala — 2012-05-26T00:01:53

Weekly on Tuesday at 1300 PDT / 2200 CET / 0400 CST

Vidyo: Dietrich's room (until we get the B2G room set up)

https://etherpad.mozilla.org/b2g-triage

This week we're kicking off with a romp through as many of the
platform bugs as we can get to: Boot2Gecko, DOM, Graphics and more.

Re: Proposal for keeping our 3.6 users secure

Alex Keybl — 2012-05-25T23:42:18

That should read "they will _not_ receive an update".

On May 25, 2012, at 4:39 PM, Alex Keybl wrote:

Re: Proposal for keeping our 3.6 users secure

Alex Keybl — 2012-05-25T23:39:40

Automatic updates from Firefox 3.6 to Firefox 12 proceeded on May 9th, and we expect automatic updates with add-on checks disabled to occur in early June. Note that this is not a force-upgrade. If users disable updates, they will receive an update.

-Alex

On May 25, 2012, at 4:28 PM, Steve Carlson wrote:

Re: Proposal for keeping our 3.6 users secure

Steve Carlson — 2012-05-25T23:28:54

What's the latest on this?  Has force-upgrade of 3.6 been tabled?

Channel/Triage Meeting - Thursday May 24th, 2012 < at > 2:00 pm PT

Lukas Blakk — 2012-05-24T19:14:49

Our next combined channel meeting is today < at > 2:00 PM PT.

Details:
* Mozilla Mountain View: Warp Core conf room, 3rd floor
* Meeting notes & triage queries: https://wiki.mozilla.org/Firefox/Channels/Meetings/2012-05-24
* Vidyo Room: Warp Core
* Vidyo Guest URL: https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym (please mute)
* Join irc.mozilla.org #planning for back channel


Cheers,
Lukas

Sync Rapid Release Meeting today, 14:00 pacfic

Allison Naaktgeboren — 2012-05-23T18:52:06

Sync will have its regular Rapid Release meeting, where we go over what is coming in upcoming releases, and the potential impact on stakeholders.

where: vidyo room 'Services'
when: 14:00 (2pm) pacific
wiki: https://wiki.mozilla.org/Services/Meetings/RapidRelease/2012-05-23

Landing plan for WebRTC

Randell Jesup — 2012-05-24T09:46:20

Here's the proposed landing plan for WebRTC.  It will land in stages
over the next month+, as portions as ready and as reviews are completed.

Undoubtedly this will be modified significantly along the way, especially
the guesses as to reviewers.

roc has already seen this; his initial comments are included.

--------------------------------------------------------------
Overview of plan to land webrtc code from Alder to Mozilla-Central:

1st tranche (preffed off in configure.in) - to land ASAP
    Build system changes:
       configure.in
       client.mk
       gyp->makefile converter
    Import script
    media/webrtc/trunk/:
        src
tools
build
test (perhaps minus test/data for now until we enable tests)
testing
    Total size: ~500K lines of .cc & .h files (plus a few .gyp files and .py files for gyp, etc), plus tests

2nd tranche: (might be swapped with some of 3rd tranche depending on 
resources) (June 1-Jun-8)
    getUserMedia with Webrtc backend (for non-mobile)
    (initial) tests for getUse

Re: Tree Action Required to Support Testing Modules

Boris Zbarsky — 2012-05-24T16:39:05

What does this mean for pushing older trees to try?  Will that break?

-Boris

Tree Action Required to Support Testing Modules

Gregory Szorc — 2012-05-24T16:17:11

tl;dr https://hg.mozilla.org/mozilla-central/rev/71075a6e5d4d needs to 
be in your tree or buildbot builds will soon fail.

https://bugzilla.mozilla.org/show_bug.cgi?id=748490 created the concept 
"testing JS modules." These are JavaScript files that can be 
loaded/imported as modules but are only available in testing code, not 
in released packages. While I'm mentioning it, I should say that you 
should consider using this instead of "head" files to provide common 
functionality to your test code because it is an architecturally 
superior solution. 
https://developer.mozilla.org/en/Developing_Tests#JavaScript_Test-Only_Modules 
has more.

To support this new feature, we need to package these test files in the 
tests archive produced during packaging. And, we need to configure 
buildbot to extract this directory when it runs tests.

Unfortunately, because of the way things work, if the "modules" 
directory is missing from the tests package and buildbot tries to 
extract this directory, the command will retur

Re: Landing plan for Webrtc

Randell Jesup — 2012-05-24T14:50:16

No, since that's all in the chrome code that will go on top of this.
(I'll verify, but there shouldn't be any I can think of.)

Re: Landing plan for Webrtc

Randell Jesup — 2012-05-24T14:49:06

See bug 'webrtc'; master tracking bug, and view the dependency tree.
(bug 665909)

Re: Landing plan for Webrtc

Wes Garland — 2012-05-24T12:53:38

I'm really looking forward to this, as I already have a "production" WebRTC
application running on Chrome Canary. Would really like a second browser
choice in case Google pushes down a breaking update (which would be totally
reasonable under the Canary release guidelines). We used the getUserMedia()
streaming video stuff to build a "photo booth" application.

I tried figuring out which bugs the WebRTC was implemented in -- it looks
like is being largely developed somewhere else than Bugzilla?

I'm now tracking Bug 749889 - Land necessary portion of media/webrtc for
getUserMedia on m-c.

Wes

On 24 May 2012 05:53, Randell Jesup <rjesup.news< at >jesup.org> wrote:

Re: Landing plan for Webrtc

Axel Hecht — 2012-05-24T12:00:24

Not really related to the landing plan, but as this is external code:

Does that come with strings that we need to localize, like error 
messages or stuff?

Axel

Landing plan for Webrtc

Randell Jesup — 2012-05-24T09:53:26

Here's the proposed landing plan for WebRTC.  It will land in stages
over the next month+, as portions as ready and as reviews are completed.

Undoubtedly this will be modified significantly along the way, especially
the guesses as to reviewers.

roc has already seen this; his initial comments are included.

--------------------------------------------------------------
Overview of plan to land webrtc code from Alder to Mozilla-Central:

1st tranche (preffed off in configure.in) - to land ASAP
    Build system changes:
       configure.in
       client.mk
       gyp->makefile converter
    Import script
    media/webrtc/trunk/:
        src
tools
build
test (perhaps minus test/data for now until we enable tests)
testing
    Total size: ~500K lines of .cc & .h files (plus a few .gyp files and .py files for gyp, etc), plus tests

2nd tranche: (might be swapped with some of 3rd tranche depending on 
resources) (June 1-Jun-8)
    getUserMedia with Webrtc backend (for non-mobile)
    (initial) tests for getUse

Firefox Developer Tools Meeting, Thu May 24

Dave Camp — 2012-05-23T19:55:15

Our weekly Firefox Developer Tools meeting is on Thursday, May 24

Agenda at: https://wiki.mozilla.org/DevTools/2012-05-24

- 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
- 650-903-0800 or 650-215-1282 x92 Conf# 99459
- 1-800-707-2533 (pin 369) Conf# 99459 (US)
- #devtools on irc.mozilla.org <irc://irc.mozilla.org/devtools> for
backchannel

Reminder: Kilimanjaro Triage today < at >1:00pm PT

Sheila Mooney — 2012-05-23T19:14:10

We are working on a Triage page (still in progress) -
https://wiki.mozilla.org/Kilimanjaro/Triage.

Details:
* Mozilla Mountain View: Peanut Butter & Jelly conf room, 3rd floor
* Dial-in: conference# 95346
* US/International: +1 650 903 0800 x92 Conf# 95346
* US toll free: +1 800 707 2533 (pin 369) Conf# 95346
* Canada: +1 416 848 3114 x92 Conf# 95346
* Vidyo: PB&J
* Join irc.mozilla.org #planning for back channel

Re: B2G/Schedule Roadmap - MozillaWiki

Dietrich Ayala — 2012-05-23T16:02:22

Those early milestones were each in the context of a particular event
(MWC, JSConf), so any work that is marked "done" is meaningful only
for that event.

As noted for Milestone 3, we're tracking all WebAPIs and apps here:
http://j.mp/Lb5ptN

It tracks design, UX, development, security reviews and testing (and
more). It's still not complete in some areas - let me know if there
are particular things you need to know that aren't visible there.

Re: B2G/Schedule Roadmap - MozillaWiki

Justin Lebar — 2012-05-23T14:48:39

That appears to be out-dated.  We have b2g and gaia mailing lists now.


Why do you think it's important what name appears in these URLs?

Note that some repositories have already moved; for example, the main
B2G repository is now https://github.com/mozilla-b2g/B2G.
_______________________________________________
dev-planning mailing list
dev-planning< at >lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-planning

Re: B2G/Schedule Roadmap - MozillaWiki

Lawrence Mandel — 2012-05-23T14:39:18

I didn't see a response to chofmann's questions (below). I'm also interested in the answers. Ping.

Lawrence

----- Original Message -----

New time for Kilimanjaro Triage - Mon/Wed < at > 1:00p -1:30p PT in MVPeanut Butter & Jelly Vidyo Rm

Sheila Mooney — 2012-05-23T05:50:19

So we are going to experiment with some new triage times starting tomorrow.
We will start with 1/2 hr at 1:00pm PT on Mon/Wed and see how that works.
Ideally, once we get going we won't need to do this as much but the more
organized group triage is necessary initially while we flush out the
requirements.

I totally understand that some people might have teams meetings and such at
that time. If it makes you feel better, I had to move mine. It's simply
impossible to find a time that works for everyone. We are hoping that most
people can make it to one of the slots or can move things around to clear
up 1/2 hr.

I will send out a calendar invite to a group of usual suspects. If I didn't
include you and you want to be added, please ping me. I will also send a
reminder prior to each meeting with the queries.

Details:
* Mozilla Mountain View: Peanut Butter & Jelly conf room, 3rd floor
* Dial-in: conference# 95346
* US/International: +1 650 903 0800 x92 Conf# 95346
* US toll free: +1 800 707 2533 (pin 369) Conf# 95