SeaMonkey/StatusMeetings/2012-06-26

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 26 June, 2012, 12:00 UTC
  • (8am Eastern, 1pm UK, 2pm Central Europe, 8pm Hong Kong)
• Location: #seamonkey IRC channel
• Further Read: Basics

Agenda

• Who's taking minutes? -> TBD
• Nominees for Friends of the Fish Tank:
  • None

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

• IanN to arrange with Jeff to send a tee-shirt or something to Serge (FotFT).
  • Still haven't managed to get hold of Serge yet.

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

• All our machines are now all out of SJC1 are are now at SCL3 or SCL1 (bug 721516).
  • Setting up SM VMs finished (bug 740613)
  • bug 744298 Straighten out OOB allocation for seamonkey HPs [fixed];
  • The R4 Macs are plugged-in, connected and base-imaged. Waiting on Callek to complete the setup.
  • cb-seamonkey-linux-01 is back in action, so we're now at 3 Linux build slaves.
• ewong and Callek are working on building on MSVC2010.
  • bug 755626 tracks the progress of changing sea-win32-02 to using MSVC2010.
  • Currently done. Trunk builds are now MSVC2010.
• L10n Update: (2012-05-20): l10n buildbots are building again on all three platforms for be, de, en-GB, es-AR, gl, hu, it, lt, nl, ru, sk, uk, zh-CN and zh-TW. Still nothing since end of April for cs, es-ES, fr, nb-NO, pl, pt-PT and sv-SE.

Release Train

• 2.11b2 shipped June 14
• 2.10.1 shipped June 16
• 2.11b3 shipped June 23
• 2.10.2 planned (no ETA yet)
  • in line with FF 13.0.2 "to help with uptake of Flash 11.3.300.262"

Extensions Compatibility Tracking

• See Basics page. Please only list current changes here.
• Addon Compatibility Listings
  • Lightning beta matching 2.11b now available on AMO.
• Our build team (Serge, Callek, ewong) needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. bug 763506

2.x (Last, Current, Next)

• 2.9 had ~X ADU by last Tuesday and 2.9.1 had ~Y downloads so far.
  • Of the released versions, as of last Tuesday, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7, E% on 2.8 and F% on 2.9. So, in the last two weeks, ~Gk (an additional H% of ADU) have migrated to 2.7 or above.
  • 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.
  • The current plan is to create a new page for latest builds available for "Legacy Platforms" e.g. PPC containing links to 2.6.1 PowerPC/G4 and also perhaps to TenFourFox and TenFourBird. We can then link to that from our main release page. See bug 759315.
• See Basics page for the usual reminders.

2.10

open tracking (0) tracking requests (8) targeted (3) fixed (16)

• One tracked 2.5 issue still open.
  • 2.1 through 2.7 have NOT included the ka (Kartvelian aka Georgian) locale. The last release with ka locale shipped was 2.0.14 and the ka l10n maintainers have not yet updated for changes in later SeaMonkey versions.
  • The plan was that Callek now needs to morph bug 667147 into removing |ka| from our [current] automation entirely (all-locales), and will look at the best locale to transition any ka users to.
    • Plan is to migrate ka users to en-US with an English dialog saying they are out of date, and a link to the all-locales page if there is a language they understand better. Current ADU of ka alone is 3-5 individuals, so low impact.~Callek
    • Callek and ewong were working on this but they didn't manage to get this done by the time 2.9 shipped. No new ETA unfortunately.
    • Seems like the ka locale maintainer finally turned up, so hopefully ka will be revived.

2.Next

• Asynchronous load-on-demand livemarks (bug 730837) landed everywhere now (incl. 2.10.1).
• [ewong:] Back in 2010 during the Dev meeting, IanN mentioned about the preferences being:
  • Too Cluttered.
  • Disorganized.
  • Old fashioned look. Since Netscape4.
  • Show fewer preferences.
• The next preference panel should:
  • Expose all preferences.
  • Different level of exposure for different people.
  • Should the next preferences be something along the lines of what bug 17199 proposes?

Feature List, Planning

Bug statistics for last two (full) weeks: 40 new, 21 fixed, 17 triaged.

• Medium triaging effort.

Open reviews/flags: 32 review 10 super-review 2 ui-review 6 feedback

• See Feature List page for major wanted/needed features.

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).

Good First Bugs:

• InvisibleSmiley has taken over bug 746110 (Expose click-to-play plugins preference in the UI) now; got r+, waiting for ui-r? from IanN (requested by Neil).
• IanN notes that it would be good if we could identify some more "Good First Bugs" for the community.

ewong

• Fixed:
  • bug 745847 - "No branch_id for a branch_name 'SeaMonkey-Release' can be found.
  • bug 760644 - E-mail composition should have a "Delivery Status Notification" option, like Thunderbird does
  • bug 764685 - install ccache on all OSX64 machines
  • bug 764862 - Select all | Copy, on the about: page (xhtml), does not paste correctly
  • bug 765443 - what is the name of cb-vmware1 and its IP?
  • bug 766502 - Bring up all new SeaMonkey Win32 VMs
  • Fumbled on 2.10.1 and 2.11b2.
  • Helped with releasing 2.11b3.

• Review:
  • bug 760942 - install python 'ssl' module on SeaMonkey Windows machines
  • bug 762264 - Help->About SeaMonkey page should link to about:rights and SeaMonkey privacy policy
  • bug 765643 - profile path in profile manager asserts error when hovering over blank
  • bug 765789 - An error occurred updating the cmd_saveAsTemplate command: TypeError: gMessageBrowser.contentPrincipal.URI is null

• Working On:
  • bug 574955 - Make webconsole work in SeaMonkey
  • bug 633937 - Port bug 562048 to suite.
  • bug 715410 - Port |Bug 352037 - Undo Add To Dictionary| to SeaMonkey
  • bug 755626 - Update mozconfigs on sea-win32-02 to build with MSVC2010
  • bug 757693 - Debug > TBPL points to an invalid URL
  • bug 762264 - Help->About SeaMonkey page should link to about:rights and SeaMonkey privacy policy

InvisibleSmiley

• Fixed:
  • bug 728726 Switch start page's Nightly detection to using navigator.buildID
  • bug 764921 Update SeaMonkey website for 2.11 Beta 2
  • bug 765469 Update SeaMonkey website for 2.10.1
  • bug 767680 Update SeaMonkey website for 2.11 Beta 3

• Working On:
  • bug 746110 Expose click-to-play plugins preference in the UI

tonymec

• ASSIGNED to nobody:

  bug 765491 porting Thunderbird bug 719413 (context menu part of Core bug 330868 "Paste Disabled After Copy from a Source That Is Not a Thunderbird Compose Window"

  Fix (port from Thunderbird) is ready but I cannot reproduce the underlying Core bug, which is "Reproducible: Sometimes" and "testcase-wanted". Waiting for someone who can, to take ownership of the bug, get review and request checkin.

Any other business?

• Geolocation
  • Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central.
  • For comm-beta all we need to do is (bug 494421) to add pref("geo.wifi.uri", "https://www.google.com/loc/json"); to browser-prefs.js. However we're not even sure we are legally allowed to ship with the URL in, we might need to actually put in a pref to disable that in newer builds.
  • No news to date. Callek will have to reach out to his MoCo legal contact again soonish.
• Test failures
  • qawanted, especially on Linux and MacOSX specific issues: reproducing and reporting would already help.
  • Serge says that on Linux and MacOSX, he just needs someone to actually run the tests and report what they see (screen, console, etc). For example, there is a Mac test about Ctrl+W not working. This should be so trivial.
  • tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.
  • IanN suggests reaching out to the user community using the newsgroups and forums.
  • Serge to do a write up and send it to Ratty to propagate to the community.
    • Ratty is ***still*** waiting for Serge.