SeaMonkey/StatusMeetings/2012-08-07

< SeaMonkey‎ | StatusMeetings
Revision as of 16:47, 5 August 2012 by Jhatlak (talk | contribs) (Created page with "<small>[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|« last meeting]] | index | [[SeaMonkey/StatusMeetings/{{#time: Y-m...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

« last meeting | index | next meeting »

SeaMonkey Meeting Details

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

  • IanN to talk to jtek about getting something sent out to Px.
  • IanN to arrange with Jeff to send a tee-shirt or something to Serge (FotFT).
    • Serge will look at the SeaMonkey Shop and let IanN know what he wants before the next meeting.

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 has been de-commissioned with extreme prejudice .
    • linux32 VM build-up.
      • sea-vm-linux32-1 was renamed from cb-sea-linux-tbox.
      • sea-vm-linux32-2 is up and running (bug 768379). We have copied this VM to 2-->6.
      • Next on our TODO is to replace -1 and remove the ams1 linux32 VM.
  • Build on MSVC2010 (ewong and Callek).
    • bug 755626 Change sea-win32-02 to using MSVC2010 [Done].
    • Trunk builds are now MSVC2010.
    • SeaMonkey Aurora has migrated to MSVC2010 and 2.12beta1 shipped with 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.
    • Issues with l10n repacks on aurora/trunk: Callek thinks this is fixed.
  • bug 775539 Build SeaMonkey using clang. In progress.
    • bug 776426 Set up ccache on all MacOSX systems.
    • bug 776428 Port |Bug 755145 - Define CCACHE_CP2 when using ccache and Clang| to SeaMonkey.
    • bug 776523 Add ac_add_options --enable-ccache to build/macosx/common [Fixed].
    • Find an interim solution for hosting tooltool binaries pending bug 768879 Have a world readable tooltool repository.

Release Train

  • 2.11b2 shipped July 27
  • 2.12b3 shipped August 3

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 ~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.
      • ADUs still falling but not as fast.
    • 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.
      • InvisibleSmiley pushed a page to the staging website and Ratty gave initial feedback.
  • See Basics page for the usual reminders.

2.11

open tracking (0) tracking requests (12) 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 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.
    • The ka owner came back with a bundle of l10n changes to get checked in. Callek to look into doing that, and try to identify if ka will be sustained going forward before completely abandoning.

2.Next

  • TBD
  • Mozilla-central bugs that affect us:
    • bug 626472 Switch from nsnull to nullptr.
      • Currently tracked in bug 776630 Switch mailnews from using nsnull to nullptr [Includes all of comm-central actually].
        • status is FIXED. Is it fixed?
    • bug 722332 Adapt main clients to asynchronous nsIBrowserSearchService API.
      • No tracking bug yet.
    • bug 774585 Update GetCodebasePrincipal callers to use the correct "data jar"
      • Currently tracked in bug 776577 Update usage in SeaMonkey of GetCodebasePrincipal to reflect changes to API (Port bug 774585).
    • bug 760940 Bookmarks and history menus behave incorrectly due to non-node weak map keys.
      • Tracked in bug 777005 Fix Bookmarks and history menus behave incorrectly due to non-node weak map keys (Port bug 760940).

Feature List, Planning

Bug statistics for last two (full) weeks: 32 new, 19 fixed, 18 triaged.

  • Good triaging effort.

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

Good First Bugs

  • Four 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,
  • Eleven have had no takers. Ratty plans to open these up to our regular contributors.
  • Neil suggests we could get some Services conversions going as GFBs.

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

IanN

InvisibleSmiley

KaiRo

mcsmurf

Misak

Mnyromyr

MReimer

Neil

Ratty

Ricardo

sgautherie

Stanimir

stefanh

tonymec

Any other business?

  • Bug Day: Should we looking to do a bug busting day in the next 3 months?
    • Useful link: [1].
    • Tonymec emailed the members@ list asking for what? when? but no replies so far. That was 10 July with a followup on the 11th.
    • IanN suggests that we go for the top 3 or 6 in the list tonymecc sent out, and probably September or October whichever is most convenient. Tonymec suggests 21-22-23 September. No objections raised.
  • 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.