SeaMonkey/StatusMeetings/2013-07-23: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(copied from 2013-07-09 minutes)
 
Line 29: Line 29:
* No Windows langpacks since 8th April on trunk. Needs investigating.
* No Windows langpacks since 8th April on trunk. Needs investigating.
** Comment from mcsmurf on this: Not clear what is meant by this, please clarify. xpi/win32/ folders on FTP server look fine. Also file a bug if something needs to be investigated/fixed.
** Comment from mcsmurf on this: Not clear what is meant by this, please clarify. xpi/win32/ folders on FTP server look fine. Also file a bug if something needs to be investigated/fixed.
* Both our buildmaster and cb-seamonkey-linux64-01 VMs are dead due to hardware failures on the Parallels host.
** sea-vm-linux64-1 has replaced cb-seamonkey-linux64-01 and is running jobs now.
** sea-master1 is now the buildmaster ({{Bug|827079}} and {{Bug|884454}}).
*  Tinderbox is EOLed. Callek has a newer version of TBPL that doesn't depend on tinderbox up and running.
*  Tinderbox is EOLed. Callek has a newer version of TBPL that doesn't depend on tinderbox up and running.
** Linux32 is fixed on trunk and aurora, windows trunk was fixed as of today. By tomorrow we'll have aurora and trunk nightlies building. Linux64 is still busted for 2.20+, Callek has a fix planned ({{Bug|890594}}).
** Linux32 is fixed on trunk and aurora, windows trunk was fixed as of today. By tomorrow we'll have aurora and trunk nightlies building. Linux64 is still busted for 2.20+, Callek has a fix planned ({{Bug|890594}}).

Revision as of 01:42, 22 July 2013

« last meeting | index | next meeting »

SeaMonkey Meeting Details

Agenda

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

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

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

  • No Windows langpacks since 8th April on trunk. Needs investigating.
    • Comment from mcsmurf on this: Not clear what is meant by this, please clarify. xpi/win32/ folders on FTP server look fine. Also file a bug if something needs to be investigated/fixed.
  • Tinderbox is EOLed. Callek has a newer version of TBPL that doesn't depend on tinderbox up and running.
    • Linux32 is fixed on trunk and aurora, windows trunk was fixed as of today. By tomorrow we'll have aurora and trunk nightlies building. Linux64 is still busted for 2.20+, Callek has a fix planned (bug 890594).
  • bug 740633 set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed.
  • comm-* will be building out of mozilla-* eventually. Jcrammer is working on this.

Fixed Stuff Since Last Meeting

  • Buildmaster up and running, although stuck behind a locked door atm.
    • Builds running and uploading, but tbpl and normal views into the process are not public.
    • ewong and Callek can manually look at builds and results, as well as generate releases
    • Callek is hand-approving requests for CLOSED TREE landings until he gets things visible enough to open the tree. (Callek only because these approvals preclude that Callek is watching results manually)

Release Train

  • SeaMonkey 2.18 was cancelled (See previous meeting notes for details). Users of 2.17.1 will be going directly to 2.19.
  • SeaMonkey 2.19 beta 1 was released on June 20th.
  • SeaMonkey 2.19 Beta 2 was released on June 26th.
    • This is the release that folds in pending release-worthy SeaMonkey patches which were awaiting approval while the tree was closed.
  • SeaMonkey 2.19 released on July 2nd.
  • SeaMonkey 2.20 beta 1 expected out on July 9th.
  • Linux64 broken on comm-central and comm-aurora due to gtk header issues, (already fixed prior to hardware failure on linux32)

Extensions Compatibility Tracking

2.x (Last, Current, Next)

  • [From a previous meeting:] There is a problem with the metrics server, so no current data is available
  • See Basics page for the usual reminders.

2.19

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

2.Next

  • Current breakages:
    • With the SeaMonkey TBPL down, Ratty has no idea what's broken and what isn't. However the Thunderbird tree is CLOSED due to multiple breakages.
    • [mozilla-central] bug 856270 Update nsEditorSpellCheck to use nsIContentPrefService2.
      • This broke comm-central in various ways:
      • SM bug 889882 Mail compose window on a reply will not allow change of To, CC, etc, nor entry of text.
      • TB bug 880595 Recent changes making spell check more async (Bug 856270) broke spell check in Thunderbird.
      • TB bug 881588 message header is read-only when compose window is reused.
      • Core bug 887010 InlineSpellChecker.addDictionaryListToMenu fails if called straight after InlineSpellChecker.enabled is set to true (and no async work around).
  • 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.
      • Mcsmurf says this is almost fixed but there was a test failure. He will close this bug and open a new one for the failure.
    • bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
    • bug 795144 default --disable-gnomeui icon theme support
      • porting bug needed for the two configure.in changesets? Changes could be folded into bug 794772 above. *** IanN and Ewong are looking into this..
    • bug 839034 move markPageAsXXX methods to nsINavHistoryService. Tracked in:
    • bug 627699 Port GTK2 to GTK3. Tracked in:

Feature List, Planning

Private Browsing is now mostly complete and uplifted to 2.18 2.19. Most things should work but some edge cases have probably been missed. Hopefully any remaining bugs will be found before its release.

  • Testing would be appreciated! Please file bugs as blocking the meta bug 460895.
  • We need to figure out if we want a new about:privatebrowsing page which someone will have to write (bug 842439).

Bug statistics for the last two (full) weeks: 31 new, 8 fixed, 9 triaged.

  • Low triaging effort.

Open reviews/flags: 23 review 7 super-review 2 ui-review 6 feedback

  • See Feature List page for major wanted/needed features.
    • Ratty suggests featuring one or more bugs from that page at each meeting.
  • Featured helpwanted bugs:

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.
  • Everyone is welcome to look at the GFBs or if they find a bug they want to tackle then ask in irc://moznet/seamonkey and we'll find a mentor if you need it.
  • New GFBs recently added:
  • Currently there are 24 GFBs open, 2 are being actively worked on.
  • List of Open mentored bugs.
    • Ratty notes that there are 23 bugs that are GFBs but without the mentor keyword. These need to be audited to see if they are really suitable as GFBs.
  • 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).

Aqualon

Callek

ewong

IanN

InvisibleSmiley

KaiRo

mcsmurf

Misak

Mnyromyr

MReimer

Neil

Ratty

rsx11m

sgautherie

stefanh

Tobin

tonymec

Any other business?

  • SeaMonkey Shop: DO NOT accept a Gift Certificate, and indeed don't put any money into a Zazzle account, unless you have a Visa, MasterCard, AmEx or similar credit card. Zazzle requires one such in lieu of an ID for every use of the funds in your account, even if you already have the necessary amount to your credit (purchases of objects, where you can change your mind until the last moment, or of gift certificates, where you can't change your mind once you've entered the details of the addressee and accepted them). In particular, European debit cards are not accepted. These procedures were (IIUC) thought up by sales suits, who never even heard of confirmation email messages with secret codes in them, unlike the "I've lost my password" procedure, which is a "technical" routine best left to lowly programmers (y'know, those who call 'mselves hackers when out of the management's hearing). Been there done that, my bad. — Tonymec (talk) 14:02, 7 July 2013 (PDT)
  • Due to time constraints InvisibleSmiley has to give up making the meeting announcements. Rsx11m has agreed to take this up on a provisional basis for the time being.