SeaMonkey/StatusMeetings/2016-03-15: Difference between revisions

m
 
(19 intermediate revisions by 5 users not shown)
Line 11: Line 11:


== Agenda ==
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''Ratty'''
* Nominees for Friends of the Fish Tank:
* Nominees for Friends of the Fish Tank:
** '''TBD'''
** '''Ewong''' for getting 2.40 out despite all odds and a broken hand.
 
=== Action Items ===
=== Action Items ===
(who needs to do what that hasn't been recorded in a bug)
(who needs to do what that hasn't been recorded in a bug)
Line 20: Line 19:


'''NEW'''
'''NEW'''
* '''IanN''' to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
* —
* —
'''OPEN'''
'''OPEN'''
Line 28: Line 28:
=== Status of the SeaMonkey Buildbot Master and Tree ===
=== Status of the SeaMonkey Buildbot Master and Tree ===
<!--Please update accordingly-->
<!--Please update accordingly-->
* Discussion:
** Ewong has managed to get uploads to the S3 servers working - mostly.
** Discussions have started with ewong, Callek, KaiRo, and others) about the route forward for both releases and infrastructure as well as growing the RelEng team and funding.
** But the build team needs to be grown as ewong is not a superhero.
** Council will have to decide if Adrian Kalla can be part of our RelEng team.
** '''FRG:''' All trees are building locally just fine with client.py fixes for chatzilla and dom-inspector. Running 2.43 now.
* Notes:
* Notes:
** Callek is winding down his involvement over the next 12 months. Possible replacement: Adrian Kalla (adriank).
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be until January at earliest.
 
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be until january at earliest.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
*** The loaner machine was decommissioned without notice.
*** Got a new loaner.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2013 would likely solve this and other bustages.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2013 would likely solve this and other bustages.
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
Line 41: Line 43:
** For various reasons we don't have a working SeaMonkey Treeherder.
** For various reasons we don't have a working SeaMonkey Treeherder.
** wrt {{bug|1155011}}, we already have a Soccoro token.  The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
** wrt {{bug|1155011}}, we already have a Soccoro token.  The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
* [2nd February 2016]
* [15th March 2016]
** [Tonymec] Building has stopped since 9 January. No tinderbox builds either. [frg] c-c would be clear to me. c-a pulls the wrong Chatzilla and Inspector again. Not sure if this is the cause. See {{Bug|1167346}}. [IanN] ewong|away has mentioned looking at Jenkins.
** [comm-central, comm-aurora and comm-beta]
*** Busted due to a host of bugs. [:ewong : currently busy fixing the mess I made with the 2.40 updating to check.]


* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
Line 51: Line 54:


=== Release Train ===
=== Release Train ===
* {{Bug|1213721}} is a tracking bug for migration from ftp.m.o to S3 for firefox and thunderbird. There's a *scary* long list of dependent bugs over there.
* Looks like ewong has managed to push 2.40 to the release servers at least for 2.40.
** How close were our staging scripts to Thunderbird's prior to the S3 migration? They were relatively divergent, primarily because we don't have signing infrastructure and Thunderbird's infra uses MoCo firefox infra, and gets a lot of process for free. We should also consult Fallen to see how Thunderbird did the migration and what sort of issues cropped up.
Discussion:
** '''Adrian Kalla''' is still producing his localized builds. Ratty suggests that we should put out a notice on the default SM start page to tell people where they can download the latest 2.4x release builds (Mozilla-release is currently at Firefox 45 which corresponds to SeaMonkey 2.42).
* '''KaiRo:''' We should get a 2.42 release done based on Gecko 45 ESR and then only concentrate on getting nightly to build and run well and ignore everything in between for the moment. We can then do as many 2.42.x security updates based on ESR as we want before we get something out of nightly that is in good shape again.
** '''IanN''' suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta "release". L10N Translations might be problematic however '''rsx11m''' says using ESR would be "safer" with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some "deal" to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that's just simple patches such as label changes or adding a checkbox). '''rsx11m''' would go with {comm,mozilla}-esr45 and merge any "safe" patches from comm-beta but that may need some talking to l10n if string changes are involved.
* Everyone agreed to skip 2.41.
** '''Adriank''' thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
* '''Frg:''' Chatzilla locale generation still broken. Frg and Adrian to deal with this.
Carried forward from discussion at last meeting:
* '''IanN''' suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta "release". L10N Translations might be problematic however '''rsx11m''' says using ESR would be "safer" with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some "deal" to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that's just simple patches such as label changes or adding a checkbox). '''rsx11m''' would go with {comm,mozilla}-esr45 and merge any "safe" patches from comm-beta but that may need some talking to l10n if string changes are involved.
* '''Adriank''' thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
<br/>
<br/>
* SeaMonkey 2.39 was released November 8th, 2015.
* SeaMonkey 2.39 was released November 8th, 2015.
<!-- I leave it up to Ratty and ewong to update the 2.40 situation -->
* '''SeaMonkey 2.40 final (tracking {{bug|1233615}}) was partially released March 14, 2016'''
* SeaMonkey 2.40 final (tracking {{bug|1233615}}) is <s>in progress:</s> in limbo.
<!-- I leave it up to Ratty and ewong to update the rest on the 2.40 release -->
** 2.40 is currently mired in a swamp so deep it makes the Marianna Trenches look like a shallow pool.
** Updating failed due to PEBKACCurrently rectifying this issue.
*** Uploading is not the problem.  It's the problem of the following facts:
**** The S3 migration did away with our stage.mo site. (It is gone)
**** Our stage.mo site scripts depended entirely on stage.mo. 
**** We need to redo our scripts to play 'pass the bucket' on the S3 server, which requires some S3 figuring out.
** Without Callek, we are stuck.
** build #4 are up for all platforms and locales
** Build #5 was tagged February 16th, but no candidate builds yet
*** Build #5 was manually taggedNot sure there'll be a build 5.
** Windows builds for #4 are signed now
** apparently there is an issue with uploading those builds to the new S3 infrastructure [https://blog.seamonkey-project.org/2016/02/04/update-on-2-40/] See {{bug|1223633}} and {{bug|1213721}}
* Merges were performed as scheduled on March 7:
* Merges were performed as scheduled on March 7:
** comm-release default is now on SM 2.42.
** comm-release default is now on SM 2.42.
Line 121: Line 117:
<!-- ** &mdash; -->
<!-- ** &mdash; -->
* Current breakages:
* Current breakages:
** {{Bug|1254987}} (Fix comm-central fallout from <tt>|{{Bug|1254410}} - Include app-specific configure files according to --enable-application/--enable-project|</tt>). All comm-central applications are not building due to {{Bug|1254410}} jcranmer, glandium, et all are looking into this.
** {{Bug|1209875}} did break any builds of 2.41+ containing a localized ChatZilla - {{bug|1213641}} filled
** {{Bug|1209875}} did break any builds of 2.41+ containing a localized ChatZilla - {{bug|1213641}} filled
<!--Please update if necessary-->
<!--Please update if necessary-->
Line 148: Line 145:


=== Feature List, Planning ===
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 8 new, 9 fixed, 9 triaged.
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 10 new, 9 fixed, 13 triaged.
* low-medium triaging effort, low number of new bugs filed.
* low-medium triaging effort, low number of new bugs filed.
* '''Ratty has a SeaMonkey build with a working Firefox Devtools!!!!''' For relevant patches see previous meeting notes.
* '''Ratty has a SeaMonkey build with a working Firefox Devtools!!!!''' For relevant patches see previous meeting notes.
Line 169: Line 166:
** The HowTo page has been moved to [[SeaMonkey/QA/Triage HowTo]]. No one having objected (or even reacted), {{bug|1092632}} is now RESOLVED FIXED. See its comment #18 for the announcement URLs.
** The HowTo page has been moved to [[SeaMonkey/QA/Triage HowTo]]. No one having objected (or even reacted), {{bug|1092632}} is now RESOLVED FIXED. See its comment #18 for the announcement URLs.
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 64 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 68 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 5 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 5 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 2 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 3 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 12 feedback]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 13 feedback]


* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
Line 205: Line 202:
==== Callek ====
==== Callek ====
==== ewong ====
==== ewong ====
* busy getting 2.40 to worry about other stuff.
** with the busted updates...  even more busy.
==== frg ====
==== frg ====
Waiting for review:
Waiting for review:
Line 210: Line 210:
* {{Bug|1188348}} data manager: domains invisible for Permissions, Preferences, Passwords. Contains string changes and hopefully will not miss the next cycle. I am done here and any changes will be need to put in new bugs.
* {{Bug|1188348}} data manager: domains invisible for Permissions, Preferences, Passwords. Contains string changes and hopefully will not miss the next cycle. I am done here and any changes will be need to put in new bugs.
* {{Bug|1251368}} SeaMonkey cookie code needs to be updated to take into account mozilla-central {{Bug|1245184}}. Might work whithout checking {{Bug|1188348}} in first but not tested. 2.44 and up affected.
* {{Bug|1251368}} SeaMonkey cookie code needs to be updated to take into account mozilla-central {{Bug|1245184}}. Might work whithout checking {{Bug|1188348}} in first but not tested. 2.44 and up affected.
* {{Bug|1250600}} Update Safebrowsing in Seamonkey for recent changes in Firefox. Follow up bug of {{Bug|920951}} Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Old Seamonkey api key does no longer work but the lists are downloaded. Ratty found out that Google thottles in this case.


Working on:
Working on:
* {{Bug|1238767}} Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.  
* {{Bug|1238767}} Localized Suite build fails in DebugQA: Stalled. I think the l10 build system might be responsible and tries to pick up files from the wrong location. Adrin Kalla thinks I need to do an l10 merge only. I disagree because the xpi only explicitly supports en-US builds.  
* {{Bug|1250600}} Update Safebrowsing in Seamonkey for recent changes in Firefox. Follow up bug of {{Bug|920951}} Update SeaMonkey Safebrowsing preferences to sync with Mozilla-Central. Old Seamonkey api key does no longer work but the lists are downloaded. Ratty found out that Google thottles in this case.


Otherwise didn't have much time in the last two weeks.  
Otherwise didn't have much time in the last two weeks. Will see what I can do next.


Tidbits (didn't see the mentiond bugs changed since the last time):
Tidbits (didn't see the mentiond bugs changed since the last time):
Line 232: Line 232:
* I absolutly hate the new Firefox build system. This seems to be based on cryptic on cryptic on cryptic scripts. Still prefer plain autoconf and configure.
* I absolutly hate the new Firefox build system. This seems to be based on cryptic on cryptic on cryptic scripts. Still prefer plain autoconf and configure.
* Alternate distribution path for Seamonkey should be evaluated. It still builds and works fine but without builds in the hands of users doesn't make much sense.
* Alternate distribution path for Seamonkey should be evaluated. It still builds and works fine but without builds in the hands of users doesn't make much sense.
* Seamonkey compiles fine under VS2015 Update 2 RC. x86 build still works fine under Windows XP SP 3 too. x64 build is stable for daily use (same with VS2013).
* I think the council should replace it's inactive members. Too much going on which needs attention.


==== IanN ====
==== IanN ====
* Usual localising, testing, reviewing, commenting and approving.
* Fixed:
* Fixed for c-c:
* Fixed for m-c:
* Fixed for m-i/fx-i:
* Pending tree opening:
* Pending approval for check in:
* Pending checkin for dependent bugs:
** {{Bug|653386}} Consider overriding netErrorApp.dtd rather than netError.dtd
* Checked in pending review:
* Waiting for feedback/review/information:
** {{Bug|1061348}} Port |{{Bug|575283}} - Cleanup mozconfig files on all platforms| to SeaMonkey
** {{Bug|1163441}} Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
* Fixing review comments before checkin:
** {{Bug|757230}} When using add button for permissions in Data Manager set a displayHost
** {{Bug|798147}} Switch to correct pref pane if pref window already open
* Working on:
** {{Bug|1252308}} Update en-GB for Gecko 45
** {{Bug|1101381}} Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
** {{Bug|1190179}} Port |{{Bug|1067325}} - Add an option to view html source in a tab| to SeaMonkey
** {{Bug|1051642}} Allow for flat chrome format when packaging extensions
** {{Bug|943335}} [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
** Various SM Council documents.
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay
** {{Bug|773979}} [META] Switch to new drag and drop api in SeaMonkey
** {{Bug|657234}} Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
** File/Folder selection in windows.
* To Do:
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.
** Prefs-in-a-tab.
** Create FAQ for Friends of the Fish Tank.
** Help get composer standalone builds working with --enable-tests.
==== InvisibleSmiley ====
==== InvisibleSmiley ====
==== KaiRo ====
==== KaiRo ====
Line 243: Line 279:
==== Rainer Bielefeld ====
==== Rainer Bielefeld ====
==== Ratty ====
==== Ratty ====
Fixed:
* {{Bug|1238428}} Workaround the <tt>NS_APP_PROFILE_DEFAULTS_{NLOC_,}50_DIR</tt> directory keys removed in {{Bug|1234012}}.
* {{Bug|1252479}} Adding the Developer Dynamically ({{Bug|1248601}}) doesn't work in SeaMonkey because it doesn't have a "browser-bottombox". [DevTools]
* {{Bug|1253846}} Port client.mk changes from {{Bug|1250294}}. [comm-central]
Needs review:
* {{Bug|1235805}} Rollup patch: Add preload content policy types for images ({{Bug|1048048}}) Use the loading document's principal to populate loadInfo for Favicons instead of using systemPrincipal ({{Bug|1119386}}) nsITaskbarPreview::Invalidate no longer throws when not visible.
* {{Bug|1222816}} Restore about:config UI (Config Editor) to old appearance by overriding Toolkit's Project Chameleon styles.
* {{Bug|1223341}} Add the Firefox Devtools to the SeaMonkey UI.
Waiting for review:
* {{Bug|1255354}} Create options to open the data manager and the addon manager in standalone windows instead of a browser tab.
* {{Bug|1255538}} Fix trailing \whitespace and \tabs in tasksOverlay.js.
Other stuff:
* Did some reviews and approvals.
* Bug triage and Bug discussions.
* Usual end user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].
==== rsx11m ====
==== rsx11m ====
Landed on comm-aurora:
Landed on comm-aurora:
* {{Bug|1245110}} Remove help about (now removed) "Ask for each cookie" option in preferences dialog.
* {{Bug|1245110}} Remove help about (now removed) "Ask for each cookie" option in preferences dialog.
Waiting for ui-review:
Waiting for ui-review (necessary?):
* {{Bug|851898}} Zoom will not go past 300%, used to be able to zoom to +/-800%.
* {{Bug|851898}} Zoom will not go past 300%, used to be able to zoom to +/-800%.
Working on:
Waiting for reviews:
* {{Bug|1251874}} Allow modification of minimum/maximum zoom levels in Content preference pane.
* {{Bug|1251874}} Allow modification of minimum/maximum zoom levels in Content preference pane.
May need retargeting:
May need retargeting:
Confirmed users
2,595

edits