SeaMonkey/StatusMeetings/2017-05-21: Difference between revisions

← Older edit

SeaMonkey/StatusMeetings/2017-05-21 (view source)

Revision as of 00:13, 22 May 2017

1,867 bytes added , 22 May 2017

→‎Action Items: corrected link to TB blog

Rsx11m

Confirmed users

2,255

edits

@@ Line 7: / Line 7: @@
 * Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
 * Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
-* Participants (in order of appearance):
+* Participants (in order of appearance): IanN frg WaltS48 called The lurker rsx11m Mc ewong tonymec
 == Agenda ==
-* Who's taking minutes? -> '''TBD'''
+* Who's taking minutes? -> '''frg'''
 * Nominees for Friends of the Fish Tank:
-** '''TBD'''
+** '''None was worthy this week'''
 === Action Items ===
@@ Line 35: / Line 35: @@
 ** frg misses an OSX try server most.
 ** There would be problems uploading binaries to Mozilla servers. Linux distributors can upload crash-symbols. This would probably be possible.
-** An infra architect  is now working for Thunderbird. The SeaMonkey project has gotten an invitation to join but nothing has been discussed yet. '''IanN''' asked '''ewong''' if he could get in touch with rkent. A new TB council has been elected and talks could start.
+** An infra architect is now working for Thunderbird. The SeaMonkey project has gotten an invitation to join but nothing has been discussed yet. '''IanN''' asked '''ewong''' if he could get in touch with rkent. A new TB council has been elected and talks could start.
 ** A joint discussion should take place. Not finalized who organizes this and when.
 ** Depending on the outcome builder software would also need to be selected. Adrian is in favor of Jenkins because buildbot expertise is rare.
@@ Line 43: / Line 43: @@
 ** There are plans by Mozilla to do cross compiles on Linux for Windows and macOS. Not finalized yet.
 ** ewong tries to set up an aws acount and starts to get things going.
+* Thunderbird announced its future plans: [https://blog.mozilla.org/thunderbird/2017/05/thunderbirds-future-home/ Thunderbird’s Future Home]
 * &mdash;
 '''CLOSED'''
-* Something needs to be done about the lack of developers and support staff or SeaMonkey will be no more in the near future.
-** '''frg''' did prepare a "asking for help" draft for the council. He is waiting for final comments and will be post it in the various SeaMonkey newsgroups. Some users are willing to proof-read and translate to other languages before it goes out. IanN will look at it after the meeting (done).
-** Council mail did go out 02/05/2017. Several discussions in the community still running. Some positive some negative. Overall a good start.
 * &mdash;
@@ Line 63: / Line 61: @@
 *** DOMi still needs to be sorted.
 *** Lightning l10n upload still needs to be sorted.
-* [7th May 2017]
+* [21st May 2017]
 ** Tests have been re-enabled to enable us to find out what's busting them. {{bug|1295826}} tracks the fixes for the Testing Infrastructure.
 *** All tests are red.
 ** All trees:
-*** {{bug|1308923}} might cause a serious problem with 2.48 and 2.49. It is still unclear if it's fixed in later releases.
+*** {{bug|1308923}} might cause a serious problem with 2.48 and 2.49. Patch in {{bug|1364977}} fixes it (updated after the meeting) and needs to go in all trees when reviewed.
 ** [comm-central]:
 *** Linux*: green
 *** OSX64: *busted* Due to mercurial issues. Tracked in {{bug|1362848}}. Might be fixed now after the meeting.
 *** Win32: busted. Been working on the puppet issue that I've missed the builds.
-*** See {{bug|1345770}} for current breakages.
+*** Builds are unusable but patches are up for all serious issues. See {{bug|1345770}} for current breakages.
+*** {{bug|1363036}} for mozilla-central needs to be fixed. Crashes SeaMonkey on tab close.
 ** [comm-beta]:
 *** Linux*: green
@@ Line 87: / Line 86: @@
 *** Was broken by uplift of {{bug|1299500}} for SeaMonkey only. {{bug|1353765}} takes care of it and should be pushed soon.
 *** See {{bug|1313304}} for current breakages.
 * Notes:
@@ Line 106: / Line 106: @@
 ** '''ewong''' will start building 2.48 when he has the csets (still waiting for l10n sign-offs).
 *** '''frg''' mailed 2.48 cset candidates to ewong and IanN. 3 l10n csets different from the Beta.
-** Updates from 2.39b1 apparently did not work, relevant for the 2.48 release to upgrade from 2.46 without problems. '''ewong''' is on it
+** Updates from 2.39b1 apparently did not work, relevant for the 2.48 release to upgrade from 2.46 without problems. '''ewong''' is on it. [ewong: For updates issue information, please look at my roundtable entry]
+** 2.48 is still the next planned release. Update needs to work for it and this is holding it up now. If this can't be fixed in 2 weeks it will be build and released without it working. 2.46 is getting old.
+** {{bug|1364977}} and {{bug|1366496}} need to be fixed for 2.48. Currently in review. Final csets will be mailed to ewong when they are checked in.
 ** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
 *** l10n problem is tracked in ({{bug|1231349}}).
@@ Line 113: / Line 115: @@
 *** See also {{Bug|652063}} (Enable localized ChatZilla builds).
 ** Release notes in {{Bug|1336315}}.
-** gtk3 will be disabled for 2.48 beta and release builds. It will be enabled for 2.49.
+** gtk3 will be disabled for 2.48 beta and release builds. It will be enabled for 2.49.1. 2.48 will be the last gtk2 build.
 *** There are at least three problems with gtk3 builds which may not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}, {{Bug|1331208}}).
 *** A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version ({{bug|1312215}}).
-*** Building releases with gtk2 is only a short time solution and will no longer be possible with Gecko 53 (SM 2.50, thus would still allow 2.49 gtk2 builds). Probably a meta bug for gtk3 compatibility should be created.
+*** A meta bug for gtk3 compatibility should be created for 2.49.1 and up.
 ** SeaMonkey 2.49 will be build with ALSA support. This has been disabled in Firefox 52 and causes problems for Linux users (see discussion in {{bug|1345661}}).
 ** Because of the following bugs updates need to be tested if they are still working:
 *** {{Bug|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
 *** {{Bug|1271761}} Add CPU features/detection to update URL
-** 2.48 is still 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
+** 2.48 is still blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
 * Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
@@ Line 156: / Line 158: @@
 * The [https://addons.mozilla.org/addon/html-validator/ HTML Validator] adds HTML validation to SeaMonkey. [https://addons.mozilla.org/en-US/firefox/addon/html-validator/versions/0.9.7.5.beta The Beta version] is no more Windows-only: it boasts support for W32/64, L32/64 and Mac 32/64 Universal in a single XPI. It does not officially support trunk builds but in Tonymec's experience it worked with them last year. It offers a choice of validators: Tidy, SGML (same algorithm as [https://validator.w3.org the W3C validator] but client-side) or both. Caveat: The toolbar button gives no results for HTML5, you need View Source for that. See [http://users.skynet.be/mgueury/mozilla/index.html the developer's site] for details.
 * In Gecko 52 obsolete toolkit parts were removed in {{bug|1312143}}. This may cause problems with older add-ons when SeaMonkey 2.49 hits the road. The 2.49 release notes should mention it. Chatzilla and DOMi were affected and were fixed.
+* There is a new build variable: MOZ_ALLOW_LEGACY_EXTENSIONS=1. It is currently set to true (1) but will be put also as a default into SeaMonkeys confvar.sh in a future bug to play it safe.
 === 2.x (Last, Current, Next) ===
 * SeaMonkey Statistics can be viewed at [https://dataviz.mozilla.org/t/public/views/SeamonkeyADI/VersionChannelADI?:embed=y#1 https://dataviz.mozilla.org] Across all channels we have an approximate ADU of 120k.
@@ Line 180: / Line 182: @@
 ==== 2.48 planned next release ====
 [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
-[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%3F tracking requests] (3)
+[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%3F tracking requests] (4)
 [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 targeted] (1)
 [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (23)
@@ Line 187: / Line 189: @@
 <!-- NOTE: Flag fields don't contain "esr" at the end -->
 [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey249&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
-[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey249&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
+[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey249&type0-0-0=equals&value0-0-0=%3F tracking requests] (6)
 [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.49 targeted] (0)
 [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey249&f2=target_milestone&f5=cf_status_seamonkey248&v2=2.49 fixed] (36)
@@ Line 221: / Line 223: @@
 === Feature List, Planning ===
-[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 19 new, 5 fixed, 21 triaged.
+[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 20 new, 7 fixed, 21 triaged.
 * comparably high triaging effort, more average number of new bugs filed.
 [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 40 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 41 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 1 ui-review]
-[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 15 feedback]
+[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 16 feedback]
 * See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
@@ Line 248: / Line 250: @@
 *** Discussion diverted to https://discourse.mozilla-community.org/t/planning-the-future-of-complete-themes/
 *** No news about it till now but will likely come with Firefox 57. Unclear if at first it can be pref controlled.
-* Rainer started a [https://unofficialseamonkeynews.wordpress.com/2016/06/01/seamonkey-bugfix-coffee-mug-competition/ Coffee-Mug-Competition]. Please let any developers you know to it and post a big '''Help wanted!''' sign.
+* Rainer does a [https://unofficialseamonkeynews.wordpress.com/2016/06/01/seamonkey-bugfix-coffee-mug-competition/ Coffee-Mug-Competition]. Please let any developers you know to it and post a big '''Help wanted!''' sign.
 * SeaMonkey Composer is outdated. Ratty thinks that using backports or parts of KompoZer [http://kompozer.net/] might solve some of the problems.
 * x64 Linux and for the first time x64 Windows builds will be made official as soon as possible.
@@ Line 258: / Line 260: @@
 ** '''IanN''' suggests doing small patches which are easier to review.
 * There are reports that the PayPal donation on the website doesn't work for USD. It seems the amount is converted to Euro (probably correct if it is a German account).
-** '''rsx11m''' filed {{Bug|1362860}}.
+** '''rsx11m''' works on {{Bug|1362860}}.
 === Roundtable - Personal Status Updates ===
@@ Line 266: / Line 268: @@
 ==== Callek ====
 ==== ewong ====
+* Updates (i.e. updating SeaMonkey via the update function) is not going to work with anything 2.48b1+.
+Why?
+Because aus2 doesn't (atm) support the newer updates paths (i.e. SSE2 etc).  I probably can try
+to figure out the aus2 code to add that support, but since this system is going, there's little
+point in hacking anything.  (If someone disagrees with me, I'm interested in knowing why.)
+So what am I doing now?  Trying to convert our aus2 updating method to using balrog.   It's
+just that it's confusing and complicated as heck.
+I liken this to translating one language *I* don't know to another language that *I* also don't know.
+(i.e German -> Russian), except with the following items:
+* With AUS2, I have the final directories which the aus2 server serves the updates.  I opted to grab the paths and work with them to translate them(and the contents) to something Balrog understands.
+* Another option that I could've done was read the whole AUS2 code and understand that; but since we aren't even trying to understand how it serves updates (which is not the same as how Balrog serves updates), there's little point in doing that.
+* Translating the paths of what aus2 produces to what Balrog understand has been a very steep uphill climb, and with the decreasing cycles I can afford to deal with this, it has been slow going.
 ==== frg ====
@@ Line 271: / Line 291: @@
 * {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Unbitrotted the patch again and did some changes so that it more or less works. The old Download Manager has been removed. I propose to put the current patch into the tree and work based on it to fix the remaining issues.
 * {{Bug|1282227}} Port Bug 1071880 and Bug 1142937 to SeaMonkey: Notifiy users of slow addons. Unable to test. Either not working or I am missing something.
-* {{Bug|1296839}} Minor Tabbrowser.xml cleanups and changes. 1/3 just needs a checkin and a last lookover wrt IanNs comment?
 * {{Bug|1356294}} Remove no longer updated languages from SeaMonkey.
 * {{Bug|1364698}} Port {{Bug|1157709}} [Remove PlacesUtils.asyncGetBookmarkIds] to SeaMonkey.
@@ Line 305: / Line 324: @@
 * {{Bug|1362860}} Update and extend donation-related information on the seamonkey-project.org website ''(initial patch)''
 ** upfront fix to change Mozilla Foundation references to SeaMonkey Association
-Ready to land on comm-central:
+Landed on comm-central:
 * {{Bug|1366122}} Set privacy.resistFingerprinting to define a default and make it discoverable
 ** basically a straight port of Firefox {{bug|1345322}}
@@ Line 311: / Line 330: @@
 * {{Bug|1362860}} Update and extend donation-related information on the seamonkey-project.org website ''(main patch)''
 ** more infos on donation process and usage
+Filed with patch posted:
+* {{Bug|1366496}} Switch usages of browser.safebrowsing.enabled to browser.safebrowsing.phishing.enabled after {{bug|1025965}}
+** Makes "Block reported web forgeries" in Privacy &amp; Security work again
+** affects 2.48 already, migration code is part of the patch
 Still planning to look into:
 * {{Bug|493217}} add UI pref for media.autoplay.enabled