SeaMonkey/StatusMeetings/2012-05-29

From MozillaWiki
Jump to navigation Jump to search

« last meeting | index | next meeting »

SeaMonkey Meeting Details

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

  • IanN to arrange with Jeff to send a tee-shirt or something to Serge (FotFT).
    • No response from The Scarlet PimpernelSerge to email, will try email again.

OPEN

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

  • All our machines are out of SJC1 are are now at SCL3 or SCL1. Everything that was up as of 2 months ago is up now. Callek still needs to set up some machines including our R4 Macs.
  • ewong and Callek are looking into building on MSVC2010 by Friday.
    • bug 755626 tracks the progress of changing sea-win32-02 to using MSVC2010.
  • cb-seamonkey-linux-01 is down due to parallels issue. dustin from #build helped us kick start it and reformatted the /build partition.
    • Callek will be redoing/has rebuilt the /build folder.
  • tonymec is worried about status of trunk l10n: 7 languages not built since Apr 27, the other 14 currently only on Linux. This is probably related to the server moves going on.
    • 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.10b2 shipped May 23

Extensions Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
    • Nothing special this time.
  • DOM Inspector Release Schedule (crussell)
    • bug 746784 Predictable release schedule for development and localization.
    • The last six weeks of a release cycle are for localizers no string changes will occur then. Localization happens on a branch (DOMI_2_0_12 right now) and concurrent development happens on default. Right now, DOM Inspector is set to ship with: de, el, en-GB, en-US, fr, ru, sk, sv-SE.
    • Serge has filed some bugs so that the relevant changes to pull the right branch are in place. See bug 732749 (client.py: review SeaMonkey policy about which extension revisions are packaged).
    • So in theory we could work out the correct tag from the Gecko version of the repos we're building in? It's not tagged it's just a branch. To get on the right branch:
 hg clone http://hg.mozilla.org/dom-inspector
 cd ./dom-inspector
 hg update DOMI_2_0_12
    • It is to be hoped that our build team (Serge, Callek, ewong) can sort it out so it is fairly automated rather than having to tweak the client.py every 6 weeks.

2.x (Last, Current, Next)

  • 2.9 had ~X ADU by last Tuesday and 2.9.1 had ~Y downloads so far (2.8 reached ~Z downloads).
    • 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 four weeks, ~Gk (an additional H% of ADU) have migrated to 2.7 or above.
  • Still a large, but slowly decreasing, chunk of users on 2.0.x.
  • Figure out what is preventing people from moving from 2.0.x to the latest versions.
    • Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.)
    • Perhaps putting resources into getting certain extensions working with SM 2.4 and above (those that won't work with SM 2.7 automatically due to compatible-by-default extensions).
    • Still need volunteers to look at what is keeping people at below 2.4. IanN could try knocking something up and send it round members lists for polishing but he's not on all the channels (mozillazine, etc) to post it to when finished.
    • Are some Linux distributions are still stuck on 2.0? We have data on OSes and OS versions in the raw data in the Mozilla metrics.
    • metrics.mozilla.org now provides us a breakdown of versions against OS.
    • There seems to be a very small number of 2.0.x users on OSes not supported by later versions. We even have some users on windows 7 using 2.0x! Fortunately Windows 8 users are at least using 2.7.
    • Darwin 9.8 is last version with PPC support, so those people may be stuck on old versions because of that.
      • For OSX/PPC I wonder if someone from the community could try building a contributed "TenFourMonkey" based on the patch sets from TenFourFox plus TenFourBird [Ratty].
      • SeaMonkey 2.6.1 for a PowerPC/G4 on Mac OS 10.5.x. IanN says we should advertise that more (and other contributed builds).
    • Ian has done some working on comparing profile of 2.0.x users against 2.9 ones.
      • Split between OS for 2.9 is Windows 92.82%, Linux 2.53%, MacOS 4.65% and for 2.0.x is Windows 85.37%, Linux 5.55%, MacOS 9.08%.
      • For those using 2.0.x on MacOS about 39% are on OSX 10.4 or above, whereas for 2.9 it is about 82%.
      • For those using 2.0.x on Linux about 98% are on Kernel 2.6, whereas for 2.9 it is about 69% (31% on 3.0 or above).
      • For those using 2.0.x on Windows about 37% are on Vista/7/2008, a further 62% are on XP/2003, whereas for 2.9 it is about 50% on Vista/7/2008 and 49% on XP/2003.
  • See Basics page for the usual reminders.

2.9

open tracking (0) tracking requests (1) targeted (3) fixed (5)

  • 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.
    • Callek now needs to morph bug 667147 into removing |ka| from our [current] automation entirely (all-locales). Callek will look at best locale to transition any ka users to.
      • Plan is to migrate ka users to en-US with a 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.
  • One regression issue noted for 2.8: bug 735946 Browser is not not focused when opening links from external applications. Fixed on 2.9+.

2.Next

  • TBD

Feature List, Planning

Bug statistics for last two (full) weeks: 41 new, 16 fixed, 6 triaged.

  • Low triaging effort...

Open reviews/flags: 20 review 9 super-review 1 ui-review 6 feedback

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

Aqualon

Callek

ewong

  • Fixed:
    • bug 408834 - Page Info violates XUL box model.
    • bug 620997 - Open "Links" URLs in browser.
    • bug 715410 - Port |Bug 352037 - Undo Add To Dictionary| to SeaMonkey
    • bug 741084 - [SeaMonkey, OSX 10.5] "[testharnessreport.js] Error 1" due to "ImportError: No module named simplejson"
    • bug 752797 - Build ID absent from about: page
  • Waiting for a Release build to see if this works:
    • bug 745847 - "No branch_id for a branch_name 'SeaMonkey-Release' can be found.
  • Review:
  • Working On:
    • bug 574955 - Make webconsole work in SeaMonkey
    • bug 755626 - Update mozconfigs on sea-win32-02 to build with MSVC2010
    • bug 757693 - Debug > TBPL points to an invalid URL

IanN

InvisibleSmiley

KaiRo

mcsmurf

Misak

Mnyromyr

MReimer

Neil

Ratty

Ricardo

sgautherie

Stanimir

stefanh

tonymec

  • business as usual
  • VERIFIED

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.
Retrieved from "https://wiki.allizom.org/index.php?title=SeaMonkey/StatusMeetings/2012-05-29&oldid=434779"