761
edits
(→ewong) |
(status updates) |
||
| Line 7: | Line 7: | ||
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel] | * Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel] | ||
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]] | * Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]] | ||
* Participants (in order of appearance): | * Participants (in order of appearance): frg tonymec rsx11m IanN | ||
== Agenda == | == Agenda == | ||
* Who's taking minutes? -> ''' | * Who's taking minutes? -> '''frg''' | ||
* Nominees for Friends of the Fish Tank: | * Nominees for Friends of the Fish Tank: | ||
** ''' | ** '''frg and ewong for getting the 2.49.2 release out of the door''' | ||
=== Action Items === | === Action Items === | ||
| Line 28: | Line 28: | ||
** Backporting bugs to 2.49 or doing an interim 2.53 build with security fixes is being evaluated. | ** Backporting bugs to 2.49 or doing an interim 2.53 build with security fixes is being evaluated. | ||
* Upcoming l10n changes to the build system which need to be monitored. | * Upcoming l10n changes to the build system which need to be monitored. | ||
** Mozilla | ** Mozilla is now checking in the first changes from [http://projectfluent.org/ Project Fluent]. The browser preferences are migrated in {{bug|1424682}} Migrate the chrome of Preferences to the new Localization AP. | ||
* New council members frg, rsx11m and ewong were already appointed a few weeks ago. '''IanN''' will look into a website update now that the project areas were updated. | * New council members frg, rsx11m and ewong were already appointed a few weeks ago. '''IanN''' will look into a website update now that the project areas were updated. | ||
* TODO: Add Adrian Kalla to RelEng team. Overall no change as of today. | * TODO: Add Adrian Kalla to RelEng team. Overall no change as of today. | ||
| Line 76: | Line 76: | ||
*** Do not expect to use the 2.57 release yet other than for brief testing. It is fundamentally broken by Mozilla source and api removals. | *** Do not expect to use the 2.57 release yet other than for brief testing. It is fundamentally broken by Mozilla source and api removals. | ||
*** Sidebar and Mail/News are broken because of XUL template removals. See {{bug|464710}}. | *** Sidebar and Mail/News are broken because of XUL template removals. See {{bug|464710}}. | ||
*** Bookmark Manager broken because of sync api removal. See {{bug|1378089}}. | *** Bookmark Manager broken because of places sync api removal. See {{bug|1378089}}. | ||
*** See {{bug|1433370}} for current 2.57 breakages. | *** See {{bug|1433370}} for current 2.57 breakages. | ||
** [comm-beta]: | ** [comm-beta]: | ||
| Line 106: | Line 106: | ||
=== Release Train === | === Release Train === | ||
'''Note''': Assuming that Gecko 60 will be the next ESR branch, SeaMonkey 2.57 (current trunk) will be the next release, thus patches with l10n-relevant strings have to land in this cycle. | '''Note''': Assuming that Gecko 60 will be the next ESR branch, SeaMonkey 2.57 (current trunk) will be the next release, thus patches with l10n-relevant strings have to land in this cycle. | ||
* '''SeaMonkey 2.49.2 was released on February 15th, | * '''SeaMonkey 2.49.2 was released on February 15th, 2018''' | ||
** Updates from older SeaMonkey versions to 2.49.2 are currently not working (including from 2.48 or 2.49.1). This has been announced on the project page. | ** Updates from older SeaMonkey versions to 2.49.2 are currently not working (including from 2.48 or 2.49.1). This has been announced on the project page. | ||
** According to the crash stats the release seems to be generally stable. | |||
** A meta bug for gtk3 compatibility has been created for 2.49.1 and up {{bug|1367257}}. | ** A meta bug for gtk3 compatibility has been created for 2.49.1 and up {{bug|1367257}}. | ||
*** Missing dropmarker in {{bug|1331208}} is fixed in 2.49.2. | *** Missing dropmarker in {{bug|1331208}} is fixed in 2.49.2. | ||
*** {{bug|1398973}} is fixed in 2.49.2. Tabs will be visually | *** {{bug|1398973}} is fixed in 2.49.2. Tabs will be visually emphasized. This will affect Windows too. | ||
*** The missing scrollbar buttons patch in {{bug|1269145}} are included in 2.49.2. A followup bug will be opened to see if it can be enhanced. | *** The missing scrollbar buttons patch in {{bug|1269145}} are included in 2.49.2. A followup bug will be opened to see if it can be enhanced. | ||
*** | *** Remaining issues are with menu borders and submenu arrows (Core {{bug|1267982}} and {{bug|1334679}}) | ||
** The Thunderbird/SeaMonkey branch in mozilla-esr52 was updated to the 52.6 release level. No additional changes compared to 2.49.1 where backported in the mozilla-esr52 branch. | ** The Thunderbird/SeaMonkey branch in mozilla-esr52 was updated to the 52.6 release level. No additional changes compared to 2.49.1 where backported in the mozilla-esr52 branch. | ||
** The trunk version has been set and tinderbox builds are already available. | ** The trunk version has been set and tinderbox builds are already available. | ||
*** {{Bug|1412639}} Image from eml file not shown in Composer will be included but depends on {{Bug|1332705}} "Edit Message as new' does not work for message from file.eml" which will not be fixed for this release. | *** {{Bug|1412639}} Image from eml file not shown in Composer will be included but depends on {{Bug|1332705}} "Edit Message as new' does not work for message from file.eml" which will not be fixed for this release. | ||
*** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content" will not be fixed for this release. | *** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content" will not be fixed for this release. | ||
*** {{Bug|1417819}} which affects image embedding in Composer will be fixed for the 2.49.2 release. | *** {{Bug|1417819}} which affects image embedding in Composer will be fixed for the 2.49.2 release. | ||
| Line 138: | Line 139: | ||
** '''frg''' maintains a local 2.53 with backported comm-central and mozilla-central fixes in case we want to do a 2.53. If this can be maintained till 52.9 will be seen. It might be possible to use Security fixes from Waterfox 56 for this too. | ** '''frg''' maintains a local 2.53 with backported comm-central and mozilla-central fixes in case we want to do a 2.53. If this can be maintained till 52.9 will be seen. It might be possible to use Security fixes from Waterfox 56 for this too. | ||
** '''IanN''' thinks we might want to do a 2.53 branch in c-r and m-r so that we can include the backported bugs. | ** '''IanN''' thinks we might want to do a 2.53 branch in c-r and m-r so that we can include the backported bugs. | ||
** Because of general changes in the m-c tree e.g. ChromeUtils.import and other enhancements backporting patches becomes more time consuming. | |||
* 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. | * 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 159: | Line 161: | ||
** DOMi was fixed for 2.55 but has been badly broken by our Mozilla "friends" again recently in 2.56. See {{bug|1429936}}. | ** DOMi was fixed for 2.55 but has been badly broken by our Mozilla "friends" again recently in 2.56. See {{bug|1429936}}. | ||
** DOMi will no longer work in any Fx58+ version. | ** DOMi will no longer work in any Fx58+ version. | ||
** The devtools can inspect chrome content but this needs to be fixed in SeaMonkey. It works in Thunderbird. | |||
*** DOMi might be retired later when this works. It is currently not built. See also {{Bug|1273222}}. | |||
** The addon-SDK has been removed. | ** The addon-SDK has been removed. | ||
** SMILE is removed in 2.57. | ** SMILE is removed in 2.57. | ||
| Line 168: | Line 172: | ||
** Candidates among others are ChatZilla, Lightning, SeaTab X2 and Version Number. | ** Candidates among others are ChatZilla, Lightning, SeaTab X2 and Version Number. | ||
*** '''tomprince''' is evaluating including Lightning in Thunderbird. | *** '''tomprince''' is evaluating including Lightning in Thunderbird. | ||
*** ChatZilla development seems to have stopped. '''IanN''' thinks he can fix it. Thunderbird includes IM now. | |||
Porting this would be another alternative after the mailpane works again. | |||
* Mozilla plans to move the Thunderbird and SeaMonkey add-ons to a new site this year. At the current point in time wo don't have any information about it. | * Mozilla plans to move the Thunderbird and SeaMonkey add-ons to a new site this year. At the current point in time wo don't have any information about it. | ||
| Line 213: | Line 219: | ||
* OSX cross-compiling | * OSX cross-compiling | ||
* '''frg''' did cross compile 2.49.2 OSX on Linux from comm-esr52 and 2.57 from comm-central sucessfully using the instructions from '''IanN''' in {{bug|1379062}}. We might need to make this work fast with the current Linux builders to still be able to compile Nightly if the last builder fails and the new MacStadium Mini Mac is not provided in time. | * '''frg''' did cross compile 2.49.2 OSX on Linux from comm-esr52 and 2.57 from comm-central sucessfully using the instructions from '''IanN''' in {{bug|1379062}}. We might need to make this work fast with the current Linux builders to still be able to compile Nightly if the last builder fails and the new MacStadium Mini Mac is not provided in time. | ||
** It is not sure if the cross-compile can create universal OSX 2.49. | ** It is not sure if the cross-compile can create universal OSX 2.49.x builds needed for plugin suppprt but this will only become urgent if the last Mac Mini dies. | ||
** Building with the 10.11 SDK currently causes problems in Firefox and macOS 10.13. This is tracked in {{bug|1391790}}. | ** Building with the 10.11 SDK currently causes problems in Firefox and macOS 10.13. This is tracked in {{bug|1391790}}. | ||
** For cross compiling a recent Rust cross package is always needed. For local use it can be extracted from any Firefox macOS taskcluster build. | ** For cross compiling a recent Rust cross package is always needed. For local use it can be extracted from any Firefox macOS taskcluster build. | ||
* We need someone to work on porting sync 1.5 over to replace legacy sync code. | * We need someone to work on porting sync 1.5 over to replace legacy sync code. | ||
<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: | |||
** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager. | ** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager. | ||
** {{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. | ||
** Sync 1.1 has been removed from the mozilla source tree. If we want | ** Sync 1.1 has been removed from the mozilla source tree. If we want Sync 1.1 to work we need to fork it. | ||
*** Pro: We control our own sync server and are not left at the mercies of Mozilla the next time they change their sync system. | *** 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). | *** Con: Can't sync with Firefox (unless someone writes a Sync 1.1 client for Firefox). | ||
| Line 229: | Line 236: | ||
** '''IanN''' suggests about:smcredits. | ** '''IanN''' suggests about:smcredits. | ||
** The mozilla credits page still must be linked because there are many SeaMonkey contributors in it and Gecko is also still the foundation we did and are building on. | ** The mozilla credits page still must be linked because there are many SeaMonkey contributors in it and Gecko is also still the foundation we did and are building on. | ||
* Tests are broken. Priority for new features or ports according to '''IanN''' is to get the code working. | |||
'''frg''' suggests splitting off the tests to separate bugs for tracking and hopefully fixing in the future. | |||
With the current dev resources at hand he is not very hopeful about fixing the tests fast. | |||
* Stalled. Needs a kick: | * Stalled. Needs a kick: | ||
| Line 241: | Line 252: | ||
** 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|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''Needs further work'''. | ** {{Bug|888915}} Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. '''Needs further work'''. | ||
* [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. | * [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. | * Nightly and Aurora updates are broken. {{bug|1321131}} might be the cause. Aurora users need to be migrated to another channel if possible. | ||
| Line 364: | Line 374: | ||
=== Any other business? === | === Any other business? === | ||
* The next meeting will be held in two weeks: Sunday March 4th, 2018, 15:00 UTC | |||
* — | * — | ||
edits