Confirmed users
2,595
edits
(→frg: status update) |
Philip Chee (talk | contribs) m (→Ratty) |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 28: | Line 28: | ||
* It was suggested that we set up own builders to become more independent of Mozilla. '''adriank''' already has a working build system based on Jenkins. '''Ratty''' and '''ewong''' would like to set up one based on buildbot. No decision needed right now but this needs to be worked out. | * It was suggested that we set up own builders to become more independent of Mozilla. '''adriank''' already has a working build system based on Jenkins. '''Ratty''' and '''ewong''' would like to set up one based on buildbot. No decision needed right now but this needs to be worked out. | ||
* A new build system should provide try builds and should us also enable doing automated tests again. | * A new build system should provide try builds and should us also enable doing automated tests again. | ||
==== Discussion ==== | |||
''Ratty screwed up and didn't update the 2017-01-10 meeting with the notes. So here they are again. sumimasen, sumimasen, honto ni sumimasen.'' | |||
Benefits for 2.49ESR as opposed to whatever is comm-release: | |||
* ESR will get security fixes for 12 months. | |||
* After that we can cherry-pick and backport stuff. FRG thinks that will give us 18+ months on ESR-49. | |||
* We want to keep XP/Vista support, plug-in support other than Flash, full themes and XUL overlay extensions for a bit longer. | |||
* It'll give us some breathing space. We can even innovate and do some feature work. We could selectively back port feature work. | |||
* But no string changes would be allowed on ESR. | |||
** [Ratty] The way Thunderbird does releases on ESR and get new string changes is to do releases on comm-beta and then copy the new strings to their ESR-L10n. | |||
* [Callek] I agree it gives some more breathing room around a release train, but as Thunderbird has noticed, doing it that way still means we need beta's, because we need to work with and track changes that are necessary for future, otherwise we're in a boat of "hey there was 100k changesets between this working esr and this broken one, what. | |||
* [Ratty] For me personally the breaking point is removal of support for XUL extensions and "Full Themes". At this point I'm going to switch my focus to ESR [FRG] The same. | |||
* '''Build System''' | |||
** Basically we need a build system that is simple but allows lets us have localised extensions. | |||
** [IanN] In an ideal world we would like to merge mozilla-ESR into comm-ESR so we have a unified repository. | |||
** This would among other things, simplify the build process, | |||
** '''jcranmer''' has been doing some testing in the Cypress twig repository but that work has stalled since jcranmer lost interest. | |||
** [FRG] Whatever is decided should be decided with TB together. I don't think we will be able to do it alone. | |||
** Will the build system we use depend on whether we join forces with TB? TB will continue to use buildbot, so the question whether we adapt to their buildbot configuration or they adapt to us. | |||
** It would it be a good idea that we come up with a basic plan of what infra we need and finalize the structure and then let Callek have a looksee? | |||
* '''Ratty''' is prepared to fork out some cash to get some independent infrastructure working. | |||
* Q: what TB are going to do about infrastructure. [Ratty] They have hired a systems architect to do the planning for their new infrastructure. | |||
* One issue that ewong is concerned about. since a lot of our current infra interact with moco-internal stuff (api tooltool and the upload servers to name a few). | |||
* We need to be able to upload those nightlies to stage (archive.m.o) and the symbol server. And eventually we'll need to be able to upload data to "Balrog" (the update server) which we'd currently need to upload that data to our own update server. | |||
** So we either ask them to whitelist those external ips or we duplicate the kind of setup they have. | |||
* FRG asks if we could put a donation page into the SeaMonkey 2.48 first start page. Instead of the regular hello new release page we could redirect to another page on seamonkey-project.org. | |||
=== Action Items === | === Action Items === | ||
Line 121: | Line 147: | ||
** Thunderbird solved l10n issues with their 49.0 beta, hopefully that procedure is transplantable to SeaMonkey. | ** Thunderbird solved l10n issues with their 49.0 beta, hopefully that procedure is transplantable to SeaMonkey. | ||
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling] | * Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling] | ||
** | ** Merges completed January 23rd (mozilla-beta → mozilla-release was merged January 16th), trunk now on SM '''2.51'''. | ||
** Because of the following bugs updates need to be tested if they are still working: | ** 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|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference | ||
Line 128: | Line 154: | ||
=== Extensions and Plugins Compatibility Tracking === | === Extensions and Plugins Compatibility Tracking === | ||
* SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. This would fix long standing issues we have with AMO. | |||
** [Ratty] Suggests that if we do this, we can also host the ''Firefox & Thunderbird Add-on Converter for SeaMonkey''. | |||
* '''Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57''' [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/]. | * '''Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57''' [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/]. | ||
** ''new'' add-ons other than WebExtensions will [[Add-ons/2017#Firefox_53|no longer be accepted for signing]] as early as Gecko 53. | ** ''new'' add-ons other than WebExtensions will [[Add-ons/2017#Firefox_53|no longer be accepted for signing]] as early as Gecko 53. | ||
Line 176: | Line 204: | ||
==== 2.48 planned next release ==== | ==== 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?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] ( | [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey248&type0-0-0=equals&value0-0-0=%3F tracking requests] (2) | ||
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 targeted] (1) | [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] ( | [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] (19) | ||
==== 2.Next ==== | ==== 2.Next ==== | ||
Line 185: | Line 213: | ||
** {{Bug|1003434}} Add support for about:sync-progress. | ** {{Bug|1003434}} Add support for about:sync-progress. | ||
** As an alternative to porting sync setting up a sync 1.1 server might work. | ** As an alternative to porting sync setting up a sync 1.1 server might work. | ||
*** Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system. | |||
*** Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox). | |||
* Stalled. Needs a kick: | * Stalled. Needs a kick: | ||
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play). | ** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play). | ||
Line 190: | Line 220: | ||
<!-- ** — --> | <!-- ** — --> | ||
* Current breakages: | * Current breakages: | ||
** Currently '''FRG''' fixes breakages faster than we can report them in our fortnightly meetings ;) | |||
** — | |||
<!-- ** — --> | <!-- ** — --> | ||
<!--Please update if necessary--> | <!--Please update if necessary--> | ||
* Mozilla-central bugs that affect us: | * Mozilla-central bugs that affect us: | ||
** {{Bug|1298243}} 'drag/drop: DataTransfer.types is wrong type'. Building SeaMonkey still works but changes probably need to be ported. | ** {{Bug|1298243}} 'drag/drop: DataTransfer.types is wrong type'. Building SeaMonkey still works but changes probably need to be ported. | ||
** {{Bug|1276739}} 'replace list.txt with a region-aware JSON file format to allow different search configs...'. Regressions for SeaMonkey are tracked in {{Bug|1300198}}. | ** {{Bug|1276739}} 'replace list.txt with a region-aware JSON file format to allow different search configs...'. Regressions for SeaMonkey are tracked in {{Bug|1300198}}. | ||
*** {{Bug|1300198}} Move list.txt over to JSON once {{bug|1276739}} is in. | |||
**** This will likely break search engines and needs to be looked at. | |||
*** | |||
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs. | ** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs. | ||
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in: | ** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in: | ||
Line 207: | Line 235: | ||
** {{Bug|825588}} Asynchronous JavaScript API for downloads and {{Bug|851471}} Decommission nsIDownloadManager. Tracked in: | ** {{Bug|825588}} Asynchronous JavaScript API for downloads and {{Bug|851471}} Decommission nsIDownloadManager. Tracked in: | ||
*** {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''frg is currently looking into the patch from Neil'''. | *** {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''frg is currently looking into the patch from Neil'''. | ||
* [frg] suggested to match SeaMonkeys minor version number with then one from Firefox in a future release. This need to be looked into first because some external releng or other stuff might rely on the -3 version offset. | * [frg] suggested to match SeaMonkeys minor version number with then one from Firefox in a future release. This need to be looked into first because some external releng or other stuff might rely on the -3 version offset. | ||
* [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion. | * [adriank] would like to drop DOMi or at least not bundling it with release builds in {{Bug|1273222}}. Open for discussion. | ||
Line 216: | Line 241: | ||
=== Feature List, Planning === | === Feature List, Planning === | ||
[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: | [http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 29 new, 24 fixed, 17 triaged. | ||
* moderately high triaging effort, back to average number of new bugs filed after the initial spike from the 2.46 release. | * moderately high triaging effort, back to average number of new bugs filed after the initial spike from the 2.46 release. | ||
[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>=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>=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 | [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-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 1 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 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 | [https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 15 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 237: | Line 262: | ||
*** [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road - Mark Surman] | *** [https://marksurman.commons.ca/2016/04/25/firefox-and-thunderbird-a-fork-in-the-road/ Firefox and Thunderbird: A Fork in the Road - Mark Surman] | ||
*** [https://groups.google.com/forum/#!msg/tb-planning/i-PSgm_VrOk/nXAkJgvIHwAJ Build and release: Mozilla's offer (on tb-planning)] | *** [https://groups.google.com/forum/#!msg/tb-planning/i-PSgm_VrOk/nXAkJgvIHwAJ Build and release: Mozilla's offer (on tb-planning)] | ||
** SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions. Check to see what Thunderbirds plan is. We might be able to share costs by sharing on add-ons site for both or even all three comm-central applications ([http://instantbird.com/ Instantbird]). | |||
* '''Fundamental core features''' Firefox/Mozilla plans to remove: | * '''Fundamental core features''' Firefox/Mozilla plans to remove: | ||
** {{Bug|1269807}} Remove support for all NPAPI plugins (except Flash) | ** {{Bug|1269807}} Remove support for all NPAPI plugins (except Flash) | ||
Line 310: | Line 336: | ||
==== Rainer Bielefeld ==== | ==== Rainer Bielefeld ==== | ||
==== Ratty ==== | ==== Ratty ==== | ||
Fixed: | |||
* {{Bug|1265881}} Location Bar Internet Search does not respect ˋEdit → Preferences → Browser → Internet Searchˊ | |||
* {{Bug|1326195}} [sidebars] "Get more sidebars" is not working. | |||
* {{Bug|1328557}} [SeaMonkey] Searchbar regression: No separator between datalist and form history entries. | |||
* {{Bug|1328897}} Update Google Search Plugin (sync with Firefox) [20161231]. | |||
* {{Bug|1328920}} Update Yahoo Search Plugin (sync with Firefox) [20161231]. | |||
* {{Bug|1329186}} (1) Use asyncOpen2() and (2) change nsILoadInfo.SEC_NORMAL to SEC_ALLOW_CROSS_ORIGIN_DATA_IS_NULL when using a SystemPrincipal. | |||
* {{Bug|1329401}} Rollup updates for FeedConverter.js sync with Firefox as at [20161231]. | |||
In Progress/waiting for review: | |||
* {{Bug|357097}} "Play a sound" textboxes are not editable, and don't disable Preview button when nothing has been selected. | |||
Investigating: | |||
* {{Bug|1234651}} ʎʇıןıqɐɹǝuןnʌ SSX pǝɹoʇS. | |||
Backburner: | |||
* {{Bug|1325982}} Reimplement keyword.URL as keyword.engine [SeaMonkey] Mozilla/core. | |||
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 ==== | ||
Looking into: | Looking into: |