Agenda

Action Items

(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.

NEW

—

OPEN

Need to reward the nominees of the friends of the fish tank from this year!

CLOSED

—

Status of the SeaMonkey Buildbot Master and Tree

No Windows langpacks since 8th April on trunk. Needs investigating.

Comment from mcsmurf on this: Not clear what is meant by this, please clarify. xpi/win32/ folders on FTP server look fine. Also file a bug if something needs to be investigated/fixed.

The Java on Linux bug has been tracked down to being due to our (SM's) build config. Basically our RelEng team needs to check whether we can switch to linking libstdc++ dynamically, like FF and TB do. See: bug 754622 Oracle/Sun Java jre1.7.0_04 and later does not work in SeaMonkey.

In the mean time, InvisibleSmiley has added the workaround to the 2.17 and 2.18 release notes.

Tinderbox is going to be EOLed. We need to move the SeaMonkey tinderboxpushlog off. See:

Mostly done now, just a few loose ends.

Callek has gotten up and running a newer version of TBPL (that doesn't depend on tinderbox) for testing. This will be deployed eventually to replace the current TBPL code we are running.

Mcsmurf needs to talk to Callek to see if tbpl can get more memory (some PHP(?) setting?) as sometimes fetching a log fails due to not enough memory (See bug 845844).

Release Train

Extensions Compatibility Tracking

There are now Lightning versions for both SM 2.17.x (Lightning 2.2b1) and SM 2.18 betas (Lightning 2.3b1) available on AMO.

Might need to point out in release notes that users needs to install the Lightning beta versions for the SeaMonkey releases (as Lightning follows Thunderbird 17.0.x release schedule)

Shipped extensions (DOMI, CZ, Venkman) compatibility:

Extensions are now compatible by default thus mitigating the issue. Although some people still disable c-b-d and run into issues.

SeaMonkey 2.18 will ship ChatZilla 0.9.90

Our build team (Callek, ewong, Serge) needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. bug 763506

Callek made some changes to the tags that SM pulls (CZ, Venkman, DOMI) for comm-central. See comm-central changeset 347b255c4810.

Nightly Tester Tools is being actively developed by xabolcs (coder) and whimboo (reviewer) to make it more compatible with comm-central in general and SeaMonkey in particular. See Issues · mozilla/nightlytt · GitHub.

2.x (Last, Current, Next)

[From a previous meeting:] There is a problem with the metrics server, so no current data is available

Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.). This even more applies to 2.10 which dropped support for Win2k and WinXP without SP2, and 2.14 dropping Mac OS X 10.5 support.

We now have a webpage for contributed builds available for "Legacy Platforms" like PPC (bug 759315)

Ratty notes that there are 23 bugs that are GFBs but without the mentor keyword. These need to be audited to see if they are really suitable as GFBs.

In the last two weeks since the previous meeting:

bug 735333 Use Services.prefs instead of preferences-service / gPrefService, in SeaMonkey code. Mcsmurf will check in the Services.prefs patches soon. IanN says that once this is done, it's worth asking people who use trunk to give those areas a good test, because we have regressed before with Services.jsm landings.

Mcsmurf did some testing on this, but need to check how to "discover" JS bugs, as they don't generate TEST-UNEXPECTED-FAIL in the log.

bug 752331 Atul had to give up on this bug due to illness. Ratty will leave this open for the time being.

Mentors of stalled bugs should try to communicate with the assignees and if they can't work on them any more to unassign/free up those bugs.

Roundtable - Personal Status Updates

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

bug 864379bug 846540 Part 4 regressed the fix in bug 708799 (WSEnable.exe.manifest: manifest authoring error c1010001) but only in VC9 builds. May be WONTFIXed if support for VC9 is officially dropped.