637
edits
Changes
status meeting
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance): tonymec frg IanN ewong rsx11m
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
** '''TBDIanN'''for being our favorite reviewer
=== Action Items ===
'''OPEN'''
* 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).
* Mozilla plans to check in l20n. Unclear what this means for comm-central and the current l10n build configs. Needs to be monitored.
** {{bug|1107635}} - Rewrite build system l10n repack rules from Makefile rules into a Python script might also affect a timely l10n repack
* Google API key for Safe BrowsingV2, V4 and Geolocation. Ewong/Callek about getting it loaded onto the build machines.
** Per {{bug|903439#c10}}, ewong confirmed that he has the Google API key. Safe Browsing keys are on the builders according to ewong. The build config config changes are not yet checked in. Ewong contacted Mozilla for a geolocation key and so far received no response. The Google API key can be used instead of the Mozilla key with some pref changes. rsx11m fixed a bug to use the Google key for now in all trees {{bug|1352850}}.
* '''IanN''' has spoken to mcsmurf about members list. Members mailing-list and council appointments are ready to be reviewed.
* —
'''CLOSED'''
* —
*** All tests are red.
** All trees:
*** Linux*: busted due to {{bug|1350506}}. While it is 'fixed', the fix undid the mercurial upgrade. So I'll need to update the mercurial package somehow.*** {{bug|1308923}} might cause problems with 2.48 and 2.49. It is still unclear if it's fixed in later releases.
** [comm-central]:
*** OSX64: green/orange
*** Win32: busted. Been working on the puppet issue that I've missed the builds.
*** See {{bug|1345770}} for current breakages.
** [comm-aurora]:
*** *removed* No longer available due to {{bug|1354818}}.
*** OSX64: green/orange
*** Win32: busted. Been working on the puppet issue that I've missed the builds.
*** See {{bug|1334779}} for current breakages.
** [comm-release]:
*** OSX64: green/orange
*** Win32: busted. Been working on the puppet issue that I've missed the builds.
*** See {{bug|1319091}} for current breakages.** [comm-esr52]:*** No automation. [Filed {{bug|1352820}}]*** Was broken by uplift of {{bug|1299500}} for SeaMonkey only. Comment from libertyernie in {{bug|1353765}} indicated that it fixed itself (Might have to do with unified sources). *** See {{bug|1313304}} for current breakages.
* Notes:
<!-- Comment out this section if nothing new fixed -->
==== Fixed Stuff Since Last Meeting ====
* Google announced V4 of the safebrowsing api. Firefox adds support for it in {{bug|1167038}} which is now mostly fixed. I think the part can be removed for now.
** Works in SeaMonkey. No additional preferences are needed after '''rsx11m''' fixed {{bug|1352849}} but for the V4 lists the Googgle API key needs to be on the server. The initial blocklists (unrelated item) were taken care of in {{bug|1358750}}.
* —
<!-- already fixed in the fortnight ending at last meeting
=== Release Train ===
* '''SeaMonkey 2.48 beta 1 released''' April 15, 2017 — ''kudos to ewong!''
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1351984}} (general beta issues in {{bug|1328886}}).** '''ewong''' will start building 2.48 when he has the csets.** 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
** 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}}).
*** See also {{Bug|652063}} (Enable localized ChatZilla builds).
** Release notes in {{Bug|1336315}}.
** gtk3 will be disabled for 2.48 beta and likely release builds. It will be enabled for 2.49.
*** 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}}).
*** {{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}}
* 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.
* ewong: Suggests the following:
** '''rsx11m''' filed {{bug|1358148}} to get status and approval flags added in bugzilla for SeaMonkey
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
* The next release after 2.48 will be 2.49.1 build from the ESR branch.
** '''frg''' asked if a version of 2.49.x.x is supported to distingush between cycles and builds. '''tonymec''' thinks this might work but '''ewong''' isn't sure if the infra can cope with this.
* Several languages seem to be no longer being updated and are missing many translations. They were removed from the website for 2.48 Beta 1. {{bug|1356294}} tracks the removal from the build files.
=== Extensions and Plugins Compatibility Tracking ===
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion.
* [rsx11m] did open bug {{bug|1305902}} for certificate pinning. Discussion if it should be enabled for SeaMonkey is still underway. '''Callek''' commented in the bug.
* Nightly and Aurora updates are broken. {{bug|1321131}} might be the cause. Aurora users need to be migrated to another channel if possible.
=== Feature List, Planning ===
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 16 new, 12 fixed, 3 triaged.
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).
==== Callek ====
==== ewong ====
Waiting for review or feedback:
* {{Bug|912031}} Removal of sync FormHistory api. Only a+ for uplift to Beta and test parts review missing. Filed {{Bug|1346850}} "guid in FormHistory notification "formhistory-remove" is always null" against toolkit.
* {{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 still needs review?
==== stefanh ====
==== tonymec ====
* {{Bug|1344411|Bug 1344411 - Lightweight themes are not supported anymore in SeaMonkey}} : RESOLVED FIXED, r=IanN, a(2.51)=IanN, 2.50-unaffected, 2.51-fixed, 2.52-fixed, verifyme
** Patch written with much needed help by frg at start and finish, tested on Windows by frg and on L64 by me by hacking the omni.ja, awaits verification on both 2.51 and 2.52 on any platform by anyone willing. (Verification on non-Linux may require an owncompiled build.)
=== Any other business? ===
* The next meeting will be held in two weeks: Sunday May 7, 2017, 14:00 UTC<!-- * —-->
