MozillaWiki

SeaMonkey/StatusMeetings/2025-08-24: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2025-08-24 (view source)

Revision as of 13:17, 14 September 2025

1,010 bytes removed ,  14 September
status meeting notes
(status meeting notes)
 
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 njsg rsx11m frg tonymec tomman




== 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'''
** '''UCyborg for maintaining an uBlock Origin classic fork'''


=== Action Items ===
=== Action Items ===
Line 52: Line 52:
*** 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''' is working on getting some grants 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 229: Line 224:
[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] (782)
[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] (782)
* '''SeaMonkey 2.53.22 beta will be released next'''.
* '''SeaMonkey 2.53.22 beta 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 ES 128 level and the dbm compatibility module has been dropped. Paasswords from pre 2.53.x builds will no longer be migrated.
* 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 312: Line 302:


* [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.
Frg
726

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1255070"