SeaMonkey/StatusMeetings/2012-04-03

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 3 April, 2012, 13:00 UTC
• Location: #seamonkey IRC channel
• Further Read: Basics

Agenda

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

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

OPEN

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

• TBD

Release Train

• 2.9b2 shipped March 30.

Extensions Compatibility Tracking

• Basics moved to new Basics page. Please only list current changes here.
• Addon Compatibility Listings
  • Lightning 1.4b2 doesn't seem to work with SM 2.9b2. :-(
  • Firebug 1.10a6 works with trunk, all issues solved. :-)

2.x (Last, Current, Next)

• 2.7 had ~X ADU by last Tuesday and 2.7.2 has 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, D% on 2.5, E% on 2.6 and F% on 2.7. So, in the last two weeks, ~Gk (an additional H% of ADU) have migrated to 2.6 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, AFAIK, Callek now also has access to that.
• Usual reminders moved to new Basics sub page.

2.8

open tracking (0) tracking requests (0) targeted (1) fixed (15)

• 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 should be able to get this done by the time 2.9 ships.

2.Next

• TBD

Feature List, Planning

Bug statistics for last two (full) weeks: 44 new, 28 fixed, 51 triaged.

• Great triaging effort! :-)

Open reviews/flags: 29 review 9 super-review 0 ui-review 6 feedback

• Major wanted/needed features moved to new Feature List page.

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

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.