Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2017-01-10: Difference between revisions
SeaMonkey/StatusMeetings/2017-01-10 (view source)
Revision as of 11:06, 24 January 2017
, 24 January 2017→Special agenda carried over for this meeting
(→Release Train: next merge day) |
Philip Chee (talk | contribs) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
== Agenda == | == Agenda == | ||
* Who's taking minutes? -> ''' | * Who's taking minutes? -> '''Ratty''' | ||
* Nominees for Friends of the Fish Tank: | * Nominees for Friends of the Fish Tank: | ||
** ''' | ** '''Ewong''' | ||
** '''FRG''' | |||
=== Special agenda carried over for this meeting === | === Special agenda carried over for this meeting === | ||
==== Release Planning next release ==== | ==== Release Planning next release ==== | ||
* Mozilla plans to remove XUL | * Mozilla plans to remove XUL, classic extensions, and full themes by the end of 2017. While it is still unclear if the time table is realistic the future outlook is bleak. | ||
* It is unclear if the current SeaMonkey | * It is unclear if the current SeaMonkey developer team can fix the upcoming build breaks fast enough to do regular releases. | ||
* SeaMonkey 2.50a1 (FF 53) is building but this may change at any time. l20n is planned for FF 53 and might disrupt l10n building again. | * SeaMonkey 2.50a1 (FF 53) is building but this may change at any time. l20n is planned for FF 53 and might disrupt l10n building again. | ||
* The consensus seems to be to do a ESR 52 cycle for the next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility. | * The consensus seems to be to do a ESR 52 cycle for the next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility. | ||
* Thunderbird | * Thunderbird has been ESR only since the beginning of the train model. The biggest obstacle/restriction is that no string changes are allowed. | ||
* Doing a 2.49 ESR will give the | * Doing a 2.49 ESR will give the developer team a breather to fix the upcoming breaks in the mozilla source tree. | ||
* Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine. | * Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine. | ||
==== Release Planning mid/long term ==== | ==== Release Planning mid/long term ==== | ||
* Mid/Long term release planning was not discussed because of time constraints. It will be put on the agenda of the next status meeting. | * Mid/Long term release planning was not discussed because of time constraints. It will be put on the agenda of the next status meeting. | ||
* 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 ==== | |||
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 108: | Line 134: | ||
** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists. | ** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists. | ||
** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46. | ** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46. | ||
* | * '''SeaMonkey 2.48 Release TBA'''. | ||
** Ready for L10N signoffs. Changesets to be provided by Callek. | |||
** | ** [rsx1m] GTK2 vs GTK3: comm-beta is still on gtk3; it appears that there is no movement in the gtk3-related bugs, thus I think we should stick with gtk2 at least for c-r until those are resolved or gtk2 is retired by a significant distro. | ||
** | ** Lightning it needs a patch for l10n which doesn't exist yet. It was during the repack where the wget failed. | ||
** ' | |||
* 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] | ||
** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th). | ** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th). | ||
| Line 168: | Line 180: | ||
** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.--> | ** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.--> | ||
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders. | * See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders. | ||
==== 2.46 current release ==== | |||
==== 2. | |||
<!-- let's maintain two sections, this one for the *current* release --> | <!-- let's maintain two sections, this one for the *current* release --> | ||
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%2B open tracking] (0) | [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%2B open tracking] (0) | ||
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1) | [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey246&type0-0-0=equals&value0-0-0=%3F tracking requests] (1) | ||
| Line 225: | Line 198: | ||
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 targeted] (0) | [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.48 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_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48 fixed] (16) | [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] (16) | ||
==== 2.Next ==== | ==== 2.Next ==== | ||
* We need someone to work on porting sync 1.5 over to replace legacy sync code. '''Frg was distracted by other bugs and tasks and didn't look into it yet'''.<br />See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in: | * We need someone to work on porting sync 1.5 over to replace legacy sync code. '''Frg was distracted by other bugs and tasks and didn't look into it yet'''.<br />See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in: | ||
| Line 254: | Line 225: | ||
** {{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'''. | ||
=== Feature List, Planning === | === Feature List, Planning === | ||
| Line 318: | Line 282: | ||
==== Callek ==== | ==== Callek ==== | ||
==== ewong ==== | ==== ewong ==== | ||
* many brain cells died to bring 2.46 to fruition... | |||
** took a breather by doing simple stuff | |||
*** closed some bugs | |||
*** fixed some simple stuff relating to mozconfigs. | |||
** currently planning c-b release stuff so getting that organized. | |||
here's hoping 2.48 won't kill off more brain cells that I can replenish. ;P | |||
==== frg ==== | ==== frg ==== | ||
| Line 354: | Line 326: | ||
==== Rainer Bielefeld ==== | ==== Rainer Bielefeld ==== | ||
==== Ratty ==== | ==== Ratty ==== | ||
Fixed: | |||
* {{Bug|1265881}} Location Bar Internet Search does not respect Edit → Preferences → Browser → Internet Search. | |||
* {{Bug|1320095}} Error: TypeError: this.browser.finder.onFindbarOpen is not a function. | |||
* {{Bug|1320442}} Port notification (doorhanger) changes from {{Bug|1315236}} to Seamonkey. | |||
* {{Bug|1323219}} Fix tabbrowser error from removal of javascript Array generics ({{Bug|1322124}}). | |||
* {{Bug|1324119}} DownloadTaskbarProgress.jsm is missing due to being removed from mozilla-central in {{Bug|1319762}}. | |||
* {{Bug|1324121}} Port {{Bug|1322609}} and {{Bug|1322414}} to suite. For reference: | |||
** {{Bug|1322609}} Get rid of content-targetable usage in tabbrowser.xml. | |||
** {{Bug|1322414}} Move content vs. content-primary distinction out of the `type` browser attribute. | |||
* {{Bug|1324204}} Cert error page: Error code link in 'Technical details' shown as html code. | |||
* {{Bug|1326195}} [sidebars] "Get more sidebars" is not working. | |||
* {{Bug|1326210}} Noticed in {{Bug|1265881}} <tt>Error: TypeError: temp is null Source File: chrome://global/content/bindings/preferences.xml Line: 1227</tt> [Toolkit] | |||
In Progress/Needs new patch: | |||
* {{Bug|357097}} "Play a sound" textboxes are not editable, and don't disable Preview button when nothing has been selected. | |||
In Progress/Needs rethink: | |||
* {{Bug|1325982}} Reimplement keyword.URL as keyword.engine [SeaMonkey]. | |||
In Progress: | |||
* {{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. | |||
TODO: | |||
* General improvements to the internet search experience in SeaMonkey including: | |||
** Fix/improve context search (search from context menu). E.g. import the context-search extension. | |||
** Improve on {{Bug|1265881}} make default search engine setting work again. | |||
** Make the search service to not LZ4 compress the search.json metadata file. | |||
Other stuff: | |||
* Did some reviews and approvals. | |||
* Bug triage and Bug discussions. | |||
==== rsx11m ==== | ==== rsx11m ==== | ||
Hot-fix landed on comm-central/comm-aurora: | Hot-fix landed on comm-central/comm-aurora: | ||
| Line 387: | Line 390: | ||
=== Any other business? === | === Any other business? === | ||
* | * Status meeting times/days. | ||