SeaMonkey/StatusMeetings/2024-09-29: Difference between revisions

Jump to navigation Jump to search

SeaMonkey/StatusMeetings/2024-09-29 (view source)

Revision as of 11:39, 20 October 2024

30 bytes removed ,  20 October 2024
status meeting notes
m (→‎Status of the SeaMonkey Source Tree: September only has 30 days, not 31 :-)
(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 WG9s frg Tobin 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'''
** '''Myckel for build fixes'''


=== Action Items ===
=== Action Items ===
Line 50: Line 50:
<!--Please update accordingly-->
<!--Please update accordingly-->
* Our infrastructure is using Azure.
* Our infrastructure is using Azure.
** '''ewong''' has been looking at Kallithea, RhodeCode and other similar tools which are needed later to automate source code management for non mozilla repos (tools, website and others).
*** Also evaluation of Ansible and Terraform going together with it is done.
** Jenkins is being set up on the builders.
*** '''ewong''' is making progress setting up automated build jobs using it. This will still take some time.
** 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.
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
* The update server will be itself updated after releasing 2.53.19.
* The update server will be itself soon be updated.
** This is transparent. No code changes needed.
** Switching from aus2 to aus5 is transparent. No code changes needed.
* '''IanN''' has started updated the in-tree config files in {{Bug|1687385}}
* '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
* Mozilla switched Windows builds to cross compile on Linux.
* Mozilla switched Windows builds to cross compile on Linux.
** This would need backports but is not 100% native (needs Wine). So currently no plans to do this for SeaMonkey.
** This would need backports but is not 100% native (needs Wine). So currently no plans to do this for SeaMonkey.
Line 139: Line 135:
** clang 6 to 17, gcc 7.1 to 13 can be used to build on Linux or clang only for macOS.
** clang 6 to 17, gcc 7.1 to 13 can be used to build on Linux or clang only for macOS.
*** 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 if you do.
*** 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.
Line 154: Line 150:
** 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.
** 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.
* The l10n master branches are being updated on heptapot and gitlab for a release.
* The l10n master branches are being updated on heptapot and gitlab for a release.
** 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 middle of 68a1 now.
*** 2.53 got all the build fixes from the wip brnach 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(working) and private class fields are the top issues which will be addressed with this branch.
Line 202: Line 200:
[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] (689)
[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] (689)
* '''SeaMonkey 2.53.20 beta''' will be released next. No eta yet.
** We want to fix it up a bit more before a release.
** If an urgent security fix is needed we will do a 2.53.19 point release.
* '''SeaMonkey 2.53.19 final''' was released on September 4th.
* '''SeaMonkey 2.53.19 final''' was released on September 4th.
** The release was tracked in {{Bug|1902849}}.
** The release was tracked in {{Bug|1902849}}.
Line 213: Line 214:
** The release has been done last week. Testing took a bit longer for personal reasons.
** The release has been done last week. Testing took a bit longer for personal reasons.
** Please help test the prerelease versions too.
** Please help test the prerelease versions too.
** It is a bit delayed
* Because of bad user agent sniffing we updated the base UA version some time ago from Gecko 68 to 91.
* Because of bad user agent sniffing we updated the base UA version some time ago from Gecko 68 to 91.
** 2.53.20 will raise the ua version to 128.
** 2.53.20 will raise the ua version to 128.
Frg
742

edits

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

Navigation menu