SeaMonkey/StatusMeetings/2012-07-24

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 24 July, 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).
  • Serge is slowly working his way through his mail backlog. Thinks his ISP blocked IanNs emails as spam.

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)
  • Set up all SM Win32 Machines. (bug 768303). (Completed)
  • 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.
  • cb-seamonkey-linux-01 is AWOL again. bug 772055
    • and is not coming back up. It has breathed its last breath. Gone. Belly up. Bought the farm. Gone to the digital valhalla.
  • Next on Callek's agenda is the linux32 VM build-up.
    • sea-vm-linux32-2 is up (bug 768379)
    • sea-vm-linux32-1 was renamed from cb-sea-linux-tbox.
• 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.
  • SeaMonkey Aurora will migrate to MSVC2010 this week, Callek will likely do the switch/checkin on Wednesday if everything else looks good.
• 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.
  • We currently have issues with l10n repacks on aurora/trunk, Callek didn't get time this past weekend to peek at it. The issue relates to some of the very complex build-system logic we have, so it will take someone with time and understanding to investigate (< 10 hours of work). Callek will try and work on this weekend.

Release Train

• 2.11 shipped July 17
• 2.12b1 shipped July 21

Extensions Compatibility Tracking

• See Basics page. Please only list current changes here.
• Addon Compatibility Listings
  • Nothing to highlight.
• 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
  • sgautherie thinks that the current DOMi branches/tags are not suitable for automatic SeaMonkey branch selection.

2.x (Last, Current, Next)

• 2.11 had ~X ADU by last Tuesday and 2.11 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, F% on 2.9, G% on 2.10 and H% on 2.11. So, in the last two weeks, ~Ik (an additional J% of ADU) have migrated to 2.7 or above.
  • Since 19th June ADU numbers have been dropping, any ideas why?
    • Firefox has also seen numbers dropping. People have suggested that this is the normal summer drop that we've seen in past years.
  • 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 seamonkey-ppc (2.10 and 2.11b3 for OSX 10.5.8) 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.11

open tracking (0) tracking requests (11) targeted (2) fixed (25)

• 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

• TBD

Feature List, Planning

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

• Medium triaging effort.

Open reviews/flags: 25 review 8 super-review 0 ui-review 7 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:

• Two weeks ago Ratty trawled through his notes and came up with a list of GFBs. See: Google groups post and Bugzilla listing.
• Of the 17 GFBs, one was fixed by Sergey (bug 767353), and three by Ekanan Ketunuti (bug 767913, bug 767916, and bug 767920).
• Three are currently assigned (bug 695255, bug 715410, and bug 767919).
• [Ratty] I probably seeded this GFB list with too many one line fixes which were all grabbed first and the harder ones mostly untouched. Perhaps in the next round we should focus more on medium difficulty GFBs. I propose to wait one more week and if there are no takers I'll encourage our regular contributors to take over the remaining GFBs. I think perhaps we should also do more publicity in the mozillazine forums and newsgroups, perhaps target existing extension authors.
• Neil suggests we could get some Services conversions going as GFBs.

InvisibleSmiley

• Fixed:
  • bug 761886 Create/Update 2.11 Release Notes
  • bug 773140 Update SeaMonkey website for 2.11 Beta 6
  • bug 776279 Update SeaMonkey website for 2.12 Beta 1

sgautherie

• Fixed SeaMonkey (related) bugs:
  • bug 758552 Port |Bug 745396 - Refactor utils functions into {Common,Crypto}Utils| to SeaMonkey
  • bug 758554 Port |Bug 727210 - Implement token server client for Sync| to SeaMonkey
  • bug 758564 Port |Bug 562431 - Rewrite WeaveCrypto as a .jsm| to SeaMonkey
  • bug 758567 Port |Bug 706545 - Implement a sync engine for apps exposed by navigator.mozApps| to SeaMonkey
  • bug 758571 Port |Bug 730989 - Refactor identity and authentication management| to SeaMonkey
  • bug 758573 Port |Bug 669547 - Fix AsyncResource (or provide an alternative) to have better callback semantics| to SeaMonkey
  • bug 758582 Port |Bug 602876 - Implement network client for credentials exchange via J-PAKE| to SeaMonkey
  • bug 758793 Port |Bug 587027 - Use as little memory as possible| to SeaMonkey
  • bug 758802 Port |Bug 664792 - Tune sync intervals according to user behaviour| to SeaMonkey
  • bug 771235 Port |Bug 754062 - Add services/notifications to services-central| (and related bugs) to SeaMonkey
  • bug 771459 Port |Bug 741587 - Browser API: Handle alert/prompt/confirm in <iframe mozbrowser>| to SeaMonkey
  • bug 771882 Port |Bug 753238 - Create a shared Identity.jsm module| to SeaMonkey
  • bug 772549 Port |Bug 737841 - Ensure we properly handle redirecting and error visits| to SeaMonkey
  • bug 773144 Port packaging changes from |Bug 753239 - Implement a DOM component for navigator.id|
  • bug 774265 Fully update packaging wrt |Bug 534956 - Sync add-ons|

Any other business?

• Bug Day: Should we looking to do a bug busting day in the next 3 months?
  • Useful link: [1].
  • We could email the members list and ask for suggestions for a set of components to target.
  • Would it be better to do it during the holidays or after they end?
• 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.