SeaMonkey/StatusMeetings/2025-09-14: Difference between revisions

status meeting notes
(→‎Release Train: plenty of fixed bugs!)
(status meeting notes)
 
(6 intermediate revisions by 3 users not shown)
Line 8: Line 8:
** if the direct link doesn't work, try [ircs://irc.libera.chat:6697/ ircs://irc.libera.chat:6697/] explicitly
** if the direct link doesn't work, try [ircs://irc.libera.chat:6697/ ircs://irc.libera.chat:6697/] explicitly
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):
* Participants (in order of appearance): IanN rsx11m frg njsg tonymec




== Agenda ==
== Agenda ==
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''frg'''
* Nominees for Friends of the Fish Tank:
* Nominees for Friends of the Fish Tank:
** '''TBD'''
** '''The new SeaMonkey council for orgainizing stuff behind the curtain'''


=== Action Items ===
=== Action Items ===
Line 51: Line 51:
** Cloning the mozilla- repos is problematic. They are huge and the process is slow.
** Cloning the mozilla- repos is problematic. They are huge and the process is slow.
*** Incremental updates need to be done whenever possible later.
*** Incremental updates need to be done whenever possible later.
** '''mcsmurf''' is working on getting some grants from Microsoft for open source projects on Azure.
** '''mcsmurf''' has got a grant from Microsoft for open source projects on Azure.
** Inital discussions have been started with [https://osuosl.org/ OSUOSL] to potentially host our infra.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
* '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
Line 72: Line 73:
** Mozilla plans to move to github and abandon mercurial. We have no plans to do this for our release branch and the website.
** Mozilla plans to move to github and abandon mercurial. We have no plans to do this for our release branch and the website.
*** This might affect future check-ins into comm-central.
*** This might affect future check-ins into comm-central.
* '''frg''' proposes to end 32 bit release support. Main reason is that modern websites are memory hungry and the 32 bit only architecture cause more and more oom crashes and subsequent complaints. Mozilla recently stopped testing Linux x86 releases too.
* 32 bit release support has ended with 2.53.22b1. Main reason is that modern websites are memory hungry and the 32 bit only architecture cause more and more oom crashes and subsequent complaints. Mozilla recently stopped testing Linux x86 releases too.
** So far building i686 is possible with gcc 8.5.0 under Rocky 8 and clang under Windows.
** So far building i686 is possible with gcc 8.5.0 under Rocky 8 Linux and clang under Windows.
** We plan to retire 32 bit builds with 2.53.22. A bookmarks import regression from 2.53.20 was fixed in 2.53.21.
** 32 bit build code will not be removed and anyone can still do x86 for fun and personal use.
** 32 bit build code will not be removed and anyone can still do x86 for fun and personal use.
*** Problems building x86 will only be fixed on a best effort base.
** Problems building x86 will only be fixed on a best effort base.
* To reduce the use of different compilers we are looking into compiling future 2.53 Windows releases with clang 14 or later.
* To reduce the use of different compilers we are looking into compiling future 2.53 Windows releases with clang 14 or later.
* VS2022 is theoretically supported but building is currently broken because of compiler changes.
* VS2022 is theoretically supported but building is currently broken because of compiler changes.
** The Windows build server will and can not be switched to it for now.
** The VS2019 toolset in VS2022 is picked for compiling if installed.
** The Windows build server will not be switched to it for now.
* Recommended Windows 10 toolkit version is 10.1.22261.x (latest sub revision).
* Recommended Windows 10 toolkit version is 10.1.22261.x (latest sub revision).
** The 10.0.20348 toolkit for Server 2022 causes a compile error with the mapi.h header.
** The 10.0.20348 toolkit for Server 2022 causes a compile error with the mapi.h header.
Line 87: Line 88:
* We are now building on Rocky Linux 8 and Windows Server 2019 since 2.53.20.
* We are now building on Rocky Linux 8 and Windows Server 2019 since 2.53.20.
** Fixing the macOS build symbols issue, later compiler support and fixing the native macOS build can now be tackled.
** Fixing the macOS build symbols issue, later compiler support and fixing the native macOS build can now be tackled.
** 2.53.19 was the last release built under CentOS 7. The minimum libstdc++ and other library levels changed with 2.53.20.
** macOS now builds on Intel macs but packaging still fails.
*** The Linux i686 builds are affected the most. Minimum base OS is now Red Hat 8 or *buntu 20 which are not available for i686.
*** Q4OS 5.7 can be used for old i686 boxes.
** We might switch to dedicated builders later because of cost savings and better performance.
* For Windows 2.53 mozbuild 3.4 is working.
* For Windows 2.53 mozbuild 3.4 is working.
** Mozbuild 4.x is currently broken for building 2.53.x because of msys2.
** Mozbuild 4.x is currently broken for building 2.53.x because of msys2.
Line 150: Line 148:
** macOS arm builds are still not possible amd would need to be notarized which means buying an Apple developer certificate at least.
** macOS arm builds are still not possible amd would need to be notarized which means buying an Apple developer certificate at least.
** clang 7 to 19 and the VS2019 toolset are supported under Windows x64.
** clang 7 to 19 and the VS2019 toolset are supported under Windows x64.
** VS2019 and VS2022 are currently not supported for compiling Windows x86.
** VS2022 can currently not be used for compiling Windows x64. New features in it need fixes in the source.
** VS2022 can currently not be used for compiling Windows x64. New features in it need fixes in the source.
*** '''frg''' added support for using the VS2019 toolset in VS2022 installations till compiling with VS2022 is fixed.
*** '''frg''' added support for using the VS2019 toolset in VS2022 installations till compiling with VS2022 is fixed.
Line 163: Line 160:
** Running under Windows 8 or Server 2012 (original not R2) is not being tested by us.
** Running under Windows 8 or Server 2012 (original not R2) is not being tested by us.
** * Current Firefox and Thunderbird only support macOS 10.14 or higher.
** * Current Firefox and Thunderbird only support macOS 10.14 or higher.
** Official Linux and Windows x86 releases might be phased out later.
*** x86 builds have a 8 times greater crash rate compared to the x64 builds. Mostly OOM crashes.
* The l10n master branches are being updated on heptapod and gitlab for a release.
* The l10n master branches are being updated on heptapod and gitlab for a release.
** Unlike the 2.53 comm and mozilla repos we do not need to do backports and can always update to the latest translations and just tag releases.
** Unlike the 2.53 comm and mozilla repos we do not need to do backports and can always update to the latest translations and just tag releases.
Line 178: Line 173:
** We currently do not have the time and resources (mostly manpower) to do notarized builds. This would need a whole new process because we are currently cross compiling under Linux.
** We currently do not have the time and resources (mostly manpower) to do notarized builds. This would need a whole new process because we are currently cross compiling under Linux.
*** For the same reasons we are also not testing Beta macOS builds.
*** For the same reasons we are also not testing Beta macOS builds.
* '''frg''' did places updates for 2.53.20. The old sync api is now gone and won't come back.
** Affected extensions need to be updated but there are few.
** The old api has been disabled some time ago and was mostly broken before 2.53.1.
* tr is now being translated and we think we can ship it with 2.53.22.
** '''frg''' merges all relevant tr strings back from the central l10n to our 2.53 repo.
* Although it does not get many updates and generates outdated code in some cases we do not plan to drop Composer.
* Although it does not get many updates and generates outdated code in some cases we do not plan to drop Composer.
** '''IanN''' would like to improve it but needs to find some time to do it first.
** '''IanN''' would like to improve it but needs to find some time to do it first.
* The NSS and NSPR libraries have been updated to the latest ESR140 level for 2.53.23b1 pre and up.
* See {{Bug|1688498}} for important current 2.53 issues and enhancement requests.
* See {{Bug|1688498}} for important current 2.53 issues and enhancement requests.


Line 229: Line 220:
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.53 targeted] (20)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.53 targeted] (20)
[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_seamonkey253&f2=target_milestone&f5=cf_status_seamonkey249&v2=2.53 fixed] (845)
[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_seamonkey253&f2=target_milestone&f5=cf_status_seamonkey249&v2=2.53 fixed] (845)
* '''SeaMonkey 2.53.22 beta will be released next'''.
* '''SeaMonkey 2.53.22 beta was done and will be released soon'''.
** NO ETA yet.
** The release is tracked in {{Bug|1960594}}.
** The release will be tracked in {{Bug|1960594}}.
** The website update are tracked in {{Bug|1985638}}.
** ChatZilla got lots of changes so please test.
** ChatZilla got lots of changes so please test.
* '''SeaMonkey 2.53.21 final was released on June 5th, 2025'''.
** The Windows release will be shipped unsigned again. Aquiring a new signing key and setting up the needed changes is still not done.
** We shipped the Windows release unsigned. Aquiring a new signing key and setting up the needed changes is still not done.
** The release was tracked in {{Bug|1960585}}.
** The website update was tracked in {{Bug|1968424}}.
** 2.53.21 was the last x86 release.
** 2.53.21 was the last x86 release.
*** We do not plan to remove the x86 build options so you can still do a x86 build for yourself.
** NSS was updated to the latest ESR 128 level and the dbm compatibility module has been dropped. Paasswords from pre 2.53.x builds will no longer be migrated.
** tr is now being translated and we will ship it with 2.53.22b1 and up.
* Some languages might need new or more translators. See [http://forums.mozillazine.org/viewtopic.php?f=3&t=3077284 help wanted for translating].
* Some languages might need new or more translators. See [http://forums.mozillazine.org/viewtopic.php?f=3&t=3077284 help wanted for translating].
* ''' frg''' proposes to skip beta releases because we get no or minimal feedback only and this delays delivering security fixes among other things.
* ''' frg''' proposes to skip beta releases because we get no or minimal feedback only and this delays delivering security fixes among other things.
** No consensus reached about it yet so we will continue with the current release Beta/GA cycle.
** No consensus reached about it yet so we will continue with the current release Beta/GA cycle.
* NSS 3.49 and up drop the dbm compatibility module. This has been restored for 2.53.2. This will be removed in a future release. Anyone not yet on 2.53.x will probably not migrate anyway.
** Distributions using the system NSS might need to adjust compile settings for this.
* The following bugs are not yet fixed in 2.53.x:
* The following bugs are not yet fixed in 2.53.x:
** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
** {{Bug|1409458}} "Privacy Issue: Replying to or forwarding an HTML e-mail with external content".
Line 292: Line 279:
* Thunderbird did discontinue classic add-ons with the ESR78 based release.
* Thunderbird did discontinue classic add-ons with the ESR78 based release.
** Mozilla removed the last traces of classic add-ons from the Gecko source code. They can no longer be installed.
** Mozilla removed the last traces of classic add-ons from the Gecko source code. They can no longer be installed.
* The old places sync api is gone as of 2.53.20b1 and won't come back. Only the new async api is and will be supported.
** Affected extensions need to be updated but there are few.
** The old api has been disabled some time ago and was mostly broken before 2.53.1.


* cZ was integrated into SeaMonkey in {{Bug|1551033}}.
* cZ was integrated into SeaMonkey in {{Bug|1551033}}.
Line 312: Line 303:


* [https://noscript.net/getit NoScript Classic 5.x] is still available. Currently 5.1.9.
* [https://noscript.net/getit NoScript Classic 5.x] is still available. Currently 5.1.9.
* [https://github.com/gorhill/uBlock-for-firefox-legacy uBlock Origin] is still available. The latest classic version is currently 1.16.4.30. It might be orphaned because the maintainer JustOff needed to defend his country as far as we know.
* [https://github.com/UCyborg/uBlock-for-firefox-legacy/releases uBlock-for-firefox-legacy] works fine. It contains some fixes and enhancements.
* [https://github.com/UCyborg/uBlock-for-firefox-legacy/releases uBlock-for-firefox-legacy] works fine too. It contains some fixes and enhancements.
* [https://addons.thunderbird.net/en-US/seamonkey/addon/session-manager/ Session Manager] is still being updated. Latest version is 0.8.1.14 and supports SeaMonkey 2.53.x.
* [https://addons.thunderbird.net/en-US/seamonkey/addon/session-manager/ Session Manager] is still being updated. Latest version is 0.8.1.14 and supports SeaMonkey 2.53.x.
* [https://enigmail.net/index.php/en/download/changelog/ Enigmail] is supported again. Big thanks.
* [https://enigmail.net/index.php/en/download/changelog/ Enigmail] is supported again. Big thanks.
Line 382: Line 372:
* generally low activity on trunk, focus on branches towards releases
* generally low activity on trunk, focus on branches towards releases
[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/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 19 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 21 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 3 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 3 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 27 feedback]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 28 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 423: Line 413:
==== ewong ====
==== ewong ====
==== frg ====
==== frg ====
I did mostly working on aligning the wip branch with 2.53, reviewing stuff from '''IanN''' and backporting some changes to 2.53 regular in the last 3 weeks. Paid work and real life got the better part of me again. Will do the 2.53.22 beta preparations next.
I did mostly working on finalizing and building 2.53.22b beta 1 and backporting the latest nss and nspr to the future 2.53.23 release in the last 3 weeks. Otherwise it was paid work and real life which got the better part of me again.


Waiting for review:
Waiting for review:
Line 432: Line 422:


Checkin ready:
Checkin ready:
* nothing
Checked in:
* {{Bug|1978825}} Add l10n tr.
* {{Bug|1978825}} Add l10n tr.
* Parts of Bug {{Bug|1964042}} for our l10n central repo.
* Parts of Bug {{Bug|1964042}} for our l10n central repo.
Checked in:
* Lots of cZ patches from '''IanN'''.


Reviewing:
Reviewing:
Line 446: Line 436:
* Trying to get dynamic imports, bigint and fields into the regular release.
* Trying to get dynamic imports, bigint and fields into the regular release.
** Working on a parallel branch to update SpiderMonkey for this and other stuff. At almost the end of 70a1 now.
** Working on a parallel branch to update SpiderMonkey for this and other stuff. At almost the end of 70a1 now.
** Stalled in the last 3 weeks but branch got updated with regular 2.53 stuff.
*** BigInt, private class fields and dynamic imports are now working there. Preliminary support for intl.locale is also in. Needs more stuff to reintegrate new regexp and optional chaining but getting closer.
*** BigInt, private class fields and dynamic imports are now working there. Preliminary support for intl.locale is also in. Needs more stuff to reintegrate new regexp and optional chaining but getting closer.
*** Support for allSettled and matchAll redone with the original mozilla patches. Passes now more tests too.
*** Support for allSettled and matchAll redone with the original mozilla patches. Passes now more tests too.
Line 464: Line 455:


Titbits:
Titbits:
* SeaMonkey is still at 2.53.22b1 pre and still as usual all is not well. Go away nothing to see here.
* SeaMonkey is now at 2.53.23b1 pre and still as usual all is not well. Go away nothing new to see here.


==== IanN ====
==== IanN ====
Line 473: Line 464:


Checked in for 2.53.22+ / comm-central:
Checked in for 2.53.22+ / comm-central:
* {{Bug|1962248}} Remove the need to load message code and static.js into network editor in cZ
* Nothing this time.
* {{Bug|1962431}} Hide Open At Startup menu items for DCC Chat/File tabs in cZ
* {{Bug|1962436}} DCC File transfer speed is calculated at infinity on fast links in cZ
* {{Bug|1964838}} Colour the security lock in cZ
* {{Bug|1964841}} Display the viewName for each tab in the statusbar in cZ
* {{Bug|1964847}} Move client header information to title and status bars in cZ
* {{Bug|1964464}} Move network lag information to the status bar in cZ
* {{Bug|1967073}} Remove unused motifSettings code from cZ
* {{Bug|1967075}} Add href link to view names in statusbar in cZ
* {{Bug|1967076}} Move network connection status information into statusbar in cZ
* {{Bug|1967078}} Move channel mode and user counts out of header in cZ
* {{Bug|1967079}} Move user header information into statusbar in cZ
* {{Bug|1967080}} Move DCC chat information from header to statusbar in cZ
* {{Bug|1971036}} Fix advanceKeyboardFocus in cZ
* {{Bug|1971037}} Provide context menu to copy view status href in cZ
* {{Bug|1971038}} Null check this.browser in context menu
* {{Bug|1972119}} Error when double clicking empty space in userlist in cZ
* {{Bug|1972121}} Remove unused Gecko 1.7.x alert rules in cZ
* {{Bug|1972122}} Remove use of removeUsers in cZ
* {{Bug|1972125}} Null check designMode in context menu
* {{Bug|1972724}} Context menu for userlist doesn't toggle both ways for sort and show modes in cZ
* {{Bug|1973395}} Move and tidy output and splash code from output-window.js to static.js in cZ
* {{Bug|1973396}} Move changeCSS code from output-window.js to static.js in cZ
* {{Bug|1973397}} Move scrollToElement function from output-window.js to static.js in cZ
* {{Bug|1973583}} Provide modern theme for cZ


Waiting for checkin:
Waiting for checkin:
* {{Bug|1642188}} Port |{{Bug|1455052}} part 12 - Remove JS uses of nsIDOMEvent| to SeaMonkey
* {{Bug|1642188}} Port |{{Bug|1455052}} part 12 - Remove JS uses of nsIDOMEvent| to SeaMonkey
* {{Bug|1985638}} Update SeaMonkey website for 2.53.22 beta 1 release


Waiting for review:
Waiting for review:
Line 507: Line 475:
* {{Bug|1687385}} Update SeaMonkey mozconfigs
* {{Bug|1687385}} Update SeaMonkey mozconfigs
* {{Bug|1951305}} Migrate the last .inc localization file to Fluent or another format
* {{Bug|1951305}} Migrate the last .inc localization file to Fluent or another format
* {{Bug|1986545}} Use PluralForm for known networks in cZ


Waiting for feedback:
Waiting for feedback:
* {{Bug|1973583}} Provide modern theme for cZ
* {{Bug|1973583}} Provide modern theme for cZ
* {{Bug|1985638}} Update SeaMonkey website for 2.53.22 beta 1 release


Working on:
Working on:
Line 536: Line 506:


=== Any other business? ===
=== Any other business? ===
* We decided to switch the meeting schedule to a 3 week interval. If the date is a holiday it will be moved up a week and then goes back to 3 weeks.
* We decided to switch the meeting schedule to a 3 week interval. If the date is a holiday it will be moved by a week and then goes back to 3 weeks.
** Should business be booming again we will probably move back to the old schedule. For now not enough traffic to justify the two week schedule.
** Should business be booming again we will probably move back to the old schedule. For now not enough traffic to justify the two week schedule.
* The next meeting will be held in three weeks on Sunday October 5th, 2025, 14:00 UTC (16:00 CET).
* The next meeting will be held in three weeks on Sunday October 5th, 2025, 14:00 UTC (16:00 CET).
* —
* —
726

edits