SeaMonkey/StatusMeetings/2012-12-11

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: 11 December, 2012, 13:00 UTC
  • (8am Eastern, 1pm UK, 2pm Central Europe, 9pm Hong Kong)
• 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

• TBD

OPEN

• Ratty filed bug 803168 [Meta] Port Installer Changes from Firefox as at 2012/10. Hopes people will help with some of the referenced bugs.

CLOSED

• TBD

Status of the SeaMonkey Buildbot Master and Tree

• Callek's been working overtime with our buildbots and he fixed problems so that our 2.15b1 could be released on time.
• Intermittent issue with Mac OSX64 Debug Leak log comprehension. Issue tracked in bug 811195 bug 774844 and bug 811199 (Port |bug 794510 Build with NO_NSPR_10_SUPPORT| to SeaMonkey). Also see possibly related Thunderbird bug 806492.
• IanN filed bug 815340 (Fix some more nullptr abuse in comm-central) together with a patch.
• All our machines are now at SCL3 or SCL1.
  • The remaining machines on Parallels are the buildmaster (cb-seamonkey-linuxmaster-01) and Linux64 (cb-seamonkey-linux64-01). These need to be migrated to ESX. Specifically:
    • sea-vm-linux64-1 will replace cb-seamonkey-linux64-01.
    • sea-master1 will replace the current buildmaster.
  • bug 740633 set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed. sea-puppet is online. Callek to set the host up as a puppet master.

Release Train

• 2.14.1 shipped November 30
• 2.15b2 shipped December 3
• 2.15b3 shipped December 7

Extensions Compatibility Tracking

• See Basics page. Please only list current changes here.
• Addon Compatibility Listings
  • Extensions are now compatible by default thus mitigating the issue. Although some people still disable c-b-d and run into issues.
  • 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.
  • Need some traction on this. IanN spoke to Serge at MozCampEU. Serge is waiting for Callek/ewong to agree what needs to happen and to say what is workable or not.
  • In the past Serge often pushed this forward for us. But with Serge on a sabbatical, Ewong thinks he should talk to Callek in getting this automated.
  • For 2.15, compat bumps were done as lined out in bug 808426.

2.x (Last, Current, Next)

• 2.14 had ~X ADU by last Sunday and ~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-2.9, E% on 2.10-2.12, F% on 2.13 and G% on 2.14. So, in the last two weeks, ~Hk (an additional I% 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, and 2.14 dropping Mac OS X 10.5 support.
  • We now have a webpage for latest builds available for "Legacy Platforms" like PPC (bug 759315)
• See Basics page for the usual reminders.

2.14

open tracking (0) tracking requests (0) targeted (0) 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. The ka l10n maintainer has made some recent updates but;
  • Callek thinks we should remove ka, unless we can get commitment from the ka person to actually update things himself instead of dumping tarballs on us and expecting us to check it in for him. Tracked in bug 667147.
• SeaMonkey 2.14 Release Notes

2.Next

• InvisibleSmiley would like to highlight bug 815012 (Mail messages corrupt after running filters) which he personally experienced and added to the Release Notes of both 2.14 and 2.15.
• InvisibleSmiley would like to ask all contributors who set bugs to FIXED to also set the Target Milestone (TM) to the current trunk version at the same time if a patch was landed. See public Bugzilla saved search "SM fixed w/o TM" for recent bugs that have TM = ---.
• Current breakages:
  • TBD
• Mozilla-central bugs that affect us:
  • Note: Please file bugs if you notice any landing on mozilla-central that might break us. Please don't depend on Ratty noticing such landings.
  • bug 769764 move proxy resolution to separate thread and remove sync api. Tracked in:
    • MailNews bug 791645 Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
  • bug 737615 Remove use of synchronous cache API from unit tests. Tracked in:
    • bug 804972 Remove synchronous calls to nsICacheSession::openCacheEntry in SeaMonkey tests.
  • bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
    • bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
    • bug 794772 Port |Bug 713802 - Build with GIO support (and drop GnomeVFS)|
    • bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
  • bug 795144 default --disable-gnomeui icon theme support
    • porting bug needed for the two configure.in changesets?
  • bug 800018 Click-to-play is broken on various websites like cnn.com or latimes.com (2nd round) (affects click-to-play in SeaMonkey)
    • bug 813963 Port |Bug 800018 - Click-to-play is broken on various websites like cnn.com or latimes.com (2nd round)| to SeaMonkey FIXED

Feature List, Planning

Bug statistics for the last two (full) weeks: 39 new, 16 fixed, 17 triaged.

• Low triaging effort.

Open reviews/flags: 24 review 7 super-review 1 ui-review 9 feedback

• See Feature List page for major wanted/needed features.
  • Out of sight out of mind. The trouble with shuffling this off to another page makes these issues less discoverable. Ratty suggests featuring one or more bugs from that page at each meeting.

Good First Bugs

• Note: The GFB list is open to all including our regular contributors.
• Ratty is working on an updated GFB list, suggestions welcome.
• Currently there are X GFBs open, Y are being actively worked on. A is delayed, and B was abandoned.
• List of Open mentored bugs.
  • Ratty notes that there are X 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:
  • TBD
• 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).

InvisibleSmiley

• Fixed:
  • bug 819538 Update SeaMonkey website for 2.15 Beta 3
  • bug 818674 "ReferenceError: manifest is not defined" in Webapps.jsm inline function readCSPs
  • bug 817682 Port |bug 675037: fullzoom callback needs to handle null currentURI|
  • bug 817672 Update SeaMonkey website for 2.15 Beta 2
  • bug 817330 testbug458898.html fails if dom.disablewindowmoveresize = true
  • bug 817326 Set character encoding in browser_fayt.js
  • bug 817315 Remove libsoundtouch following bug 816576
  • bug 817111 Update SeaMonkey website for 2.14.1
  • bug 815801 Remove all of the site specific user agent overrides as part of backing out bug 588909 [port bug 815743]
  • bug 814984 Update SeaMonkey website for 2.15 Beta 1

Any other business?

• Bug Day:
  • Useful link: [1], also see [2] for results.
• 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.
  • Ratty to liaise with Serge when he gets back on doing a write up how the community can help us with this.