MozillaWiki

SeaMonkey/StatusMeetings/2025-01-05: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2025-01-05 (view source)

Revision as of 13:28, 26 January 2025

374 bytes removed ,  26 January
status meeting notes
(remove "2" from l10n)
(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 frg 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'''
** '''ewong for release management and as IanN stated server wrangling'''


=== Action Items ===
=== Action Items ===
Line 68: Line 68:
** 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 a new builder and 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.
* The '''WG9s''' servers are working fine and unofficial builds are being released.
* 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.
** Mirroring between gitlab and heptapod is being discussed.
** Mirroring between gitlab and heptapod is being discussed.
Line 80: Line 79:
* 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 Windows build server will and can not be switched to it for now.
* The latest Windows 10 toolkit 10.0.20348 for Server 2022 causes a compile error with the mapi.h header.
* Recommended Windows 10 toolkit version is 10.1.22261.x (latest).
** Recommended version is still 10.0.19041.
** The 10.0.20348 toolkit for Server 2022 causes a compile error with the mapi.h header.
** The Windows 11 toolkits 10.0.22xxx.x can also be used. The MAPI header was fixed by Microsoft in them.
** 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.
** Native arm support for macOS and Windows is looked into for a later date.
** Native arm support for macOS and Windows is looked into for a later date.
* We plan to update builders with a future 2.53.x release soon.
* We are now building on Rocky Linux 8 and Windows Server 2019 since 2.53.20.
** CentOS 7 reached EOL.
** Fixing the macOS build symbols issue, later compiler support and fixing the native macOS build can now be tackled.
** '''ewong''' has set up a Rocky 8 and Server 2019 builder.
** 2.53.19 was the last release built under CentOS 7. The minimum libstdc++ and other library levels changed with 2.53.20.
*** Fixing the macOS build symbols issue, later compiler support and fixing the native macOS build can now be tackled.
*** The linux i686 builds are affected the most. Minimum base os is now Red Hat 8 or *buntu 20 which are not avaialable for i686.
*** 2.53.19 was the last release built under CentOS 7. 2.53.20 and up will be build on Rocky 8. The minimum libstdc++ will change to the current Mozilla Firefox level.
*** Q4OS 5.7 can be used for old i686 boxes.
*** The server itself will be decommisioned later.
** The old build servers will be decommisioned later.
*** EOL for 2012 R2 is 2023 but has been extended in Azure.
** We might switch to dedicated builders later because of cost savings and better performance.
** 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.
Line 125: Line 123:
* The 2.53.x development builds are based on the last 56 release changesets in our [https://foss.heptapod.net/seamonkey heptapod] comm-release and mozilla-release repos.
* The 2.53.x development builds are based on the last 56 release changesets in our [https://foss.heptapod.net/seamonkey heptapod] comm-release and mozilla-release repos.
** For building please apply the patches from our [https://gitlab.com/frg/seamonkey-253-patches/ gitlab 2.53 patch queue].
** For building please apply the patches from our [https://gitlab.com/frg/seamonkey-253-patches/ gitlab 2.53 patch queue].
** An updated unofficial 2.53.x is available from [http://www.wg9s.com/comm-253/ WG9's website]. We accept filing bugs against it.
** Archived 2.53.x prerelease builds are also available from [https://archive.seamonkey-project.org/nightly/index.html nightly website].
** Archived 2.53.x builds are also available from [https://www.wg9s.com/seamonkey-253-nightly/ WG9's archive website].
** If you want to build the latest release without pending fixes you need to check out the desired branch from our [https://gitlab.com/seamonkey-project/ gitlab] repos.
** If you want to build the latest release without pending fixes you need to check out the desired branch from our [https://gitlab.com/seamonkey-project/ gitlab] repos.
** A cross reference is available at [http://xr.thereisonlyxul.org/seamonkey-2.53/ Cross-Reference seamonkey-2.53].
** A cross reference is available at [http://xr.thereisonlyxul.org/seamonkey-2.53/ Cross-Reference seamonkey-2.53].
Line 138: Line 135:
* l10n translations are not 100% complete for some languages. If you notice missing translations in your language consider opening an account on [https://pontoon.mozilla.org/ pontoon] and help with translation.
* l10n translations are not 100% complete for some languages. If you notice missing translations in your language consider opening an account on [https://pontoon.mozilla.org/ pontoon] and help with translation.
** The site is incompatible with SeaMonkey so you need a different browser for this.
** The site is incompatible with SeaMonkey so you need a different browser for this.
* Compiler support is up to date.
* Compiler support is more or less up to date for Linux and Windows.
** clang 6 to 17, gcc 7.1 to 13 can be used to build on Linux or clang only for macOS.
** clang 9 to 14 can be used to build on Linux for macOS. Later versions cause a startup craah.
** macOS sdk 13 or higher can currently not be used. The binary will not start because of some linkage issue.
** clang 6 to 17, gcc 7.1 to 13 can be used to build on Linux. Later clang versions might work too.
*** clang 15 and higher is currently not supported with macOS builds. Resulting binary crashes on startup.
*** clang 15 and higher is currently not supported with macOS builds. Resulting binary crashes on startup.
*** macOS sdk 13 or higher can currently not be used. The binary will not start because of some linkage issue.
** 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 17, VS2017 15.9.13+ and VS2019 are supported under Windows x64.
** clang 7 to 17, VS2017 15.9.13+ and VS2019 are supported under Windows x64. Later clang versions might work.
** VS2019 and VS2022 are currently not supported for compiling Windows x86.
** 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.
Line 149: Line 147:
** Mozilla skipped clang 10 support because of unspecified problems and did go straight to clang 11 from 9. We will not support clang 10 either. It can be used but is unsupported by us. gcc 9 and up did not get much/any testing so ymmv.
** Mozilla skipped clang 10 support because of unspecified problems and did go straight to clang 11 from 9. We will not support clang 10 either. It can be used but is unsupported by us. gcc 9 and up did not get much/any testing so ymmv.
* Native macOS builds are broken. Will be fixed with more build infra backports.
* Native macOS builds are broken. Will be fixed with more build infra backports.
* Current Firefox and Thunderbird only support macOS 10.14 or higher. We support macOS version 10.11 or higher.
* Cross-Reference sources are available at [http://xr.thereisonlyxul.org/seamonkey-2.53/ SeaMonkey 2.53 current].
* Cross-Reference sources are available at [http://xr.thereisonlyxul.org/seamonkey-2.53/ SeaMonkey 2.53 current].
* enable-elfhack does not work with clang and lld as linker under Linux.
* enable-elfhack does not work with clang and lld as linker under Linux.
** They are no plans to drop macOS 10.11 to 10.14, Windows 7 or 8.1 x64 support.
** '''They are no plans to drop macOS 10.11 to 10.14, Windows 7 or 8.1 x64 support.'''
** Windows server 2008 R2 and later are also supported.
** Windows server 2008 R2 and later are also supported.
** 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.
** Official Linux and Windows x86 releases might be phased out later.
** 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. Nostly OOM crashes.
*** x86 builds have a 8 times greater crash rate compared to the x64 builds. Nostly OOM crashes.
Line 160: Line 158:
** Unlike the 2.53 comm and mozilla repros we do not need to do backparts and can always update to the latest translations and just tag releases.
** Unlike the 2.53 comm and mozilla repros we do not need to do backparts and can always update to the latest translations and just tag releases.
** The l10n translations for the next release will be kept in the patch queue until it tagged for building and it s branch for the regular fixes has been checked in.
** The l10n translations for the next release will be kept in the patch queue until it tagged for building and it s branch for the regular fixes has been checked in.
** '''frg''' tries to add support for later javascript syntax features in a separate wip patch queue. Progressing nicely and middle of 68a1 now.
** '''frg''' tries to add support for later javascript syntax features in a separate wip patch queue. Progressing nicely and at the end of 68a1 now.
*** 2.53 got all the build fixes from the wip brnach as a start.
** The branch is located at [https://gitlab.com/frg/seamonkey-wip/-/tree/next-level-stuff?ref_type=heads SeaMonkey 2.53 wip branch].
*** 2.53 got all the build fixes from the wip branch as a start.
** Builds from this branch are not very usable right now because the preliminary support for optional chaining and regexp needed to be removed for a full rebase later.
** Builds from this branch are not very usable right now because the preliminary support for optional chaining and regexp needed to be removed for a full rebase later.
*** Missing support for dynamic imports (working), big int(working) and private class fields are the top issues which will be addressed with this branch.
*** Missing support for dynamic imports (working), big int (mostly working) and private class fields are the top issues which will be addressed with this branch.
* Apple borked ruuning unsigned applications starting with macOS 15.1 This is not a SeaMonkey problem. A workaround is described in {{Bug|1924612}}.
* Apple borked running unsigned applications in macOS 15.1 This is not a SeaMonkey problem. A workaround is described in {{Bug|1924612}}.
** We currently do not have the time and resources (mostly manpower) to do notarized builds. This would need a whole new process becuase we are currently cross compiling under Linux.
** Apple fixed this in macOS 15.2.
** The bug affects lots of other applications and Apple is silent and does nothing about it.
** 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.
++ '''frg''' did places updates and would see that the current 2.53 prerelease is being testing. The old sync api is now gone and won't come back.
*** 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.
*** It should not affect extensions because the old api has been disabled some time ago and was mostly broken before 2.53.1.
*** It should not affect extensions because the old api has been disabled some time ago and was mostly broken before 2.53.1.
* 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 178: Line 178:
*** This will not give you a working suite.
*** This will not give you a working suite.
*** The installer still works...
*** The installer still works...
* comm-central builds will no longer be published on the unofficial site.
* comm-central builds will no longer be published because not working.
* {{Bug|1611647}} was filed for SeaMonkey to do the rename from xul to xhtml files and references.
* {{Bug|1611647}} was filed for SeaMonkey to do the rename from xul to xhtml files and references.
** It has been done but not been checked in yet because other checkins would need to be rebased constantly then.
** It has been done but not been checked in yet because other checkins would need to be rebased constantly then.
* See {{Bug|1452448}} for current comm-central issues. This is not up to date.
* Mozilla will switch to github in the future. We expect MZLA/Thunderbird to remove the suite source in this move.
* Thunderbird plans to check in their source as a branch in mozilla-central and drop the suite code.
** We are evaluating options. Best would be to still have the source code in together with Thunderbird otherwise we would need to merge mozilla and Thunderbird changes into a new repo.
** We are evaluating options. Best would be to still have the source code in together with Thunderbird otherwise we would need to merge mozilla and Thunderbird changes into a new repo.
** A unified repo will be slow and cumbersome to handle in any case.
** A unified repo from different sources will be slow and cumbersome to handle in any case.
** This seems to be currently on hold.
* If building fails because of a missing wasi-sysroot your need to add "ac_add_options --without-wasm-sandboxed-libraries" in the mozconfig.
* If building fails because of a missing wasi-sysroot your need to add "ac_add_options --without-wasm-sandboxed-libraries" in the mozconfig.
** You can also download the wasi-sysroot from [https://github.com/WebAssembly/wasi-sdk/releases/ wasi-sysroot] manually.
** You can also download the wasi-sysroot from [https://github.com/WebAssembly/wasi-sdk/releases/ wasi-sysroot] manually.
* Builds may fail if the rust code in comm-central is not in sync with mozilla-central.
* Builds may fail if the rust code in comm-central is not in sync with mozilla-central.
* l10n support for comm-central has moved to [https://hg.mozilla.org/projects/comm-l10n comm-l10n].
* l10n support for Firefox has moved to [https://github.com/mozilla-l10n/firefox-l10n firefox-l10n].
* The l10n strings for Thunderbird and SeaMonkey are now in the [https://hg.mozilla.org/projects/comm-l10n comm-l10n] repo.
* The l10n strings for Thunderbird are now in the [https://github.com/thunderbird/thunderbird-l10n thunderbird-l10n] repo.
* The l10n strings for SeaMonkey are now in the [https://gitlab.com/seamonkey-project/seamonkey-central-l10n/ seamonkey-central-l10n] repo.
** This does not affect 2.53 builds which use back merged strings from the upstream l10n repos.
** This does not affect 2.53 builds which use back merged strings from the upstream l10n repos.
** Patches for build breakage and new reviewed functionality in suite have been checked in.
* comm-central has been updated but needs another round of minor changes WG9s did to build.
** mozilla plans to move to github. We expect MZLA to follow and need to evalutate later how central source updates can be done.
* See {{Bug|1452448}} for current comm-central issues. This is not up to date.
* '''WG9s''' incorporated some patches from '''Tobin''' into the central. patch queue. First goal is to show some ui at least.
* comm-central has been updated but needs another round of minor changes WG9s did to build. Mozilla moved config code around.  


<!-- Comment out this section if nothing new fixed -->
<!-- Comment out this section if nothing new fixed -->
Line 211: Line 208:
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.53 targeted] (19)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.53 targeted] (19)
[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] (690)
[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] (690)
* '''SeaMonkey 2.53.20 beta''' will be released next.
* '''SeaMonkey 2.53.20 Final''' will be released soon.
** We want to fix it up a bit more before a release.
** The release was done yesterday because of our Windows signing key expiring on January 6th.
** If an urgent security fix is needed we will do a 2.53.19 point release.
** The release is tracked in {{Bug|1933499}}.
** We plan to do the Beta in Early November and to release the final version at the end of November.
** The website update is tracked in {{Bug|1939950}}.
* '''SeaMonkey 2.53.20 beta''' will be released soon.
** The release is tracked in {{Bug|1902851}}.
** The website update is tracked in {{Bug|1933498}}.
** While the source has been updated extensively it is again mostly groundwork which we would like to get out for broader testing.
** While the source has been updated extensively it is again mostly groundwork which we would like to get out for broader testing.
** Please help test the prerelease versions too.
* 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 241: Line 234:


* Apple broke running unsigned applications in macOS 15.1. This has been fixed in 15.2.
* Apple broke running unsigned applications in macOS 15.1. This has been fixed in 15.2.
** There is nothing we could do short of notarizing SeaMonkey which is currently not an option becuase of not enough hours in the day.
** There is nothing we could do short of notarizing SeaMonkey which is currently not an option because of not enough hours in the day.
** {{Bug|1924612}} contains a workaround for user stuck at 15.1.x.
** {{Bug|1924612}} contains a workaround for user stuck at 15.1.x.
** This is not the first tiem Apple broke us so be careful before you switch to a new macOS version.
** This is not the first tiem Apple broke us so be careful before you switch to a new macOS version.
Line 560: Line 553:


==== tonymec ====
==== tonymec ====
==== WG9s ====


=== Any other business? ===
=== Any other business? ===
Frg
726

edits

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