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

merge previous status meeting notes in
(changes due to the meeting being moved)
(merge previous status meeting notes in)
Line 48: Line 48:
=== Status of the SeaMonkey Infrastructure ===
=== Status of the SeaMonkey Infrastructure ===
<!--Please update accordingly-->
<!--Please update accordingly-->
* Our infrastructure is using Azure.
* We are moving our infrastructure to [https://osuosl.org/ OSUOSL].
** Cloning the mozilla- repos is problematic. They are huge and the process is slow.
** Our infrastructure used Azure but we are moving it over to OSUOSL for cost and performance reasons.
*** Incremental updates need to be done whenever possible later.
** The website is now hosted by OSUOSL.
** '''mcsmurf''' has got a grant from Microsoft for open source projects on Azure.
** Preparations are already underway to move archives and builders over.
** We are moving our infrastructure to [https://osuosl.org/ OSUOSL] soon.
** The Linux Builder OS will stay at Rocky 8 to not add new libary dependencies to our releases.
** Preparations are already underway starting with the website and archives.
*** Redhat 10 and its clones also moved to x86-64-v3 which shuts out every CPU before Haswell.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
*** We still support x86-64-v1 CPUs for now. v2 might become mandatory later.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus/ Infrastructure Status (currently outdated)]
* '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
* '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
* '''ewong''' continues updating the configs and has set up some tasks on the Windows builder.
* '''ewong''' continues updating the configs and has set up some tasks on the Windows builder.
Line 64: Line 65:
** '''ewong''' set up the downloads archive in our Azure CDN for now.
** '''ewong''' set up the downloads archive in our Azure CDN for now.
** Some cost cutting measures were implemented.
** Some cost cutting measures were implemented.
* We moved to bugsplat.com for crash reports with 2.53.18b1
* We use bugsplat.com for crash reports.
** We currently are not generating crash reporter symbols for macOS releases.
** We currently are not generating crash reporter symbols for macOS releases.
** This might not get fixed soon because it needs a new builder and more fixes in the source tree for later clang and rust versions.
** This might not get fixed soon because it needs more fixes in the source tree for later clang and rust versions.
** '''frg''' tried locally in a Rocky 8 vm and the generated symbols turned out to be incomplete.
** '''frg''' tried locally in a Rocky 8 vm and the generated symbols turned out to be incomplete.
* We have created repos at [https://foss.heptapod.net/seamonkey hg heptapod] to mirror some of our code.
* We have created repos at [https://foss.heptapod.net/seamonkey hg heptapod] to mirror some of our code.
Line 76: Line 77:
* 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.
* 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 Linux and clang under Windows.
** So far building i686 is possible with gcc 8.5.0 under Rocky 8 Linux and clang under Windows.
** 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 or 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.
Line 82: Line 83:
** The VS2019 toolset in VS2022 is picked for compiling if installed.
** The VS2019 toolset in VS2022 is picked for compiling if installed.
** The Windows build server will not be switched to it for now.
** The Windows build server will not be switched to it for now.
* VS2026 drops Windows 7 and 8.1 support and will not be supported or looked into for now.
** Life is too short to follow all what MS does and don't ask about AI doing work yet.
* 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.
** Mozilla encountered some problems with the 22261 toolkit and Windows 7 support but so for no problems.
** Mozilla encountered some problems with the 22261 toolkit and Windows 7 support but so for no problems.
* Preliminary aarch64 support for Linux has been added to 2.53.
* Preliminary aarch64 support for Linux has been added to 2.53.
Line 222: 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] (893)
[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] (893)
* '''SeaMonkey 2.53.23 Final will be released next'''.
** We fixed some regressions which crept into 2.53.22b1 so we will skip the Beta.
** We fixed 2 regressions plus the Linux Close crash and alos made recaptcha work again.
* '''SeaMonkey 2.53.22 Final has been released October 31st, 2025'''.
* '''SeaMonkey 2.53.22 Final has been released October 31st, 2025'''.
** The release was tracked in {{Bug|1985637}}.
** The release was tracked in {{Bug|1985637}}.
** The website updates were tracked in {{Bug|1995623}}.
** The website updates were tracked in {{Bug|1995623}}.
** Older DOMi preferences {{Bug|1985637}} is fixed in it.
** Older DOMi preferences {{Bug|1985637}} is fixed in it.
* '''SeaMonkey 2.53.22 beta was released on September 22nd, 2025'''.
** The release was tracked in {{Bug|1960594}}.
** The website updates were tracked in {{Bug|1985638}}.
** ChatZilla got lots of changes so please test.
** The Windows release will be shipped unsigned again. Aquiring a new signing key and setting up the needed changes is still not done.
** 2.53.21 was the last x86 release.
** 2.53.21 was the last x86 release.
** 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 shipped with 2.53.22b1.
* 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.
Line 277: Line 275:
** {{Bug|1388317}}, {{Bug|1083458}} and {{Bug|1389510}} were backported to 2.53. Please check and try to fix extensions still using these features. With this done backporting is much easier now.
** {{Bug|1388317}}, {{Bug|1083458}} and {{Bug|1389510}} were backported to 2.53. Please check and try to fix extensions still using these features. With this done backporting is much easier now.
** {{Bug|1374847}} was backported to 2.53.17b1 pre and some extensions like prefbar need a simple fix.
** {{Bug|1374847}} was backported to 2.53.17b1 pre and some extensions like prefbar need a simple fix.
*** nsIPrefBranch2 and nsIPrefBranchInternal needs to be changed to nsIPrefBranch.
*** nsIPrefBranch2 and nsIPrefBranchInternal need to be changed to nsIPrefBranch.


* We broke at least one Jetpack add-on "Dark Background and Light text" with recent changes.
* We broke at least one Jetpack add-on "Dark Background and Light text" with recent changes.
742

edits