SeaMonkey/StatusMeetings/2025-02-16: Difference between revisions

SeaMonkey/StatusMeetings/2025-02-16 (view source)

Revision as of 14:08, 16 February 2025

518 bytes added , 16 February 2025

merge previous status meeting notes in

Frg

742

edits

@@ Line 30: / Line 30: @@
 * We want to create a gitlab patch/fixes repo for classic XUL extensions.
 ** '''IanN''' is looking into it.
-* Mozilla finally decided to fully cut us loose in Q3. Formally and legally this is all in order.
+* Mozilla finally decided to fully cut us loose in Q3 2023. Formally and legally this is all in order.
 ** Source code will probably be removed from comm-central because it seems parts of MZLA and/or the Thunderbird council are eager to do the same.
 ** Fortunately we are mostly independent already and it will not affect the 2.53 line or building releases.
@@ Line 39: / Line 39: @@
 ** We are currently evaluating options together with Mozilla.
 *** Source code, Pontoon translations and Bugzilla are the three items we would like to keep as is. Needs to be decided higher up at Mozilla.
-*** We got a preliminary approval note to extend our stay on the other Mozilla infrastructure till the end of 2024 but need to formalize some things till then.
+*** We got a preliminary approval note to extend our stay on the other Mozilla infrastructure.
-* Fix website for google group changes.
+** Currently no further movement and we just wait it out.
-** Dev group was discontinued and the SeaMonkey support list is more or less on life support.
+* Add '''tobins''' new [https://seamonkey.thereisonlyxul.org/ SeaMonkey community site] to the website support section.
-* c-c logbot is back so update the support section on the website.
-** '''frg''' is a slacker.
 '''CLOSED'''
@@ Line 54: / Line 52: @@
 *** Incremental updates need to be done whenever possible later.
 * Please see [https://wiki.mozilla.org/User:Ewong/infrastatus Infrastructure Status]
-* The update server will be itself soon be updated.
-** Switching from aus2 to aus5 is transparent. No code changes needed.
 * '''IanN''' has started updating the in-tree config files in {{Bug|1687385}}
 * Mozilla switched Windows builds to cross compile on Linux.
@@ Line 74: / Line 70: @@
 ** 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 checkins into comm-central.
-* '''frg''' proposes to end 32 bit release support in 2024. 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.
+* '''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.
-** No consensus reached about it yet. So far building it is possible with gcc 8.3.1 under CentOS 7 and clang under Windows.
+** So far building i686 is possible with gcc 8.5.0 under Rocky 8 and clang under Windows.
+** We plan to retire 32 bit builds with 2.53.22. 2.53.20 has at least one bookmarks import regression and we want to fix it in the last official 2.53.21 x86 build.
+** 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.
 * 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.
 ** The Windows build server will and can not be switched to it for now.
-* Recommended Windows 10 toolkit version is 10.1.22261.x (latest).
+* 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.
@@ Line 107: / Line 106: @@
 ** We need to evaluate options to be able to use them on the builder and locally for developer testing.
 ** Azure CodeVault might be the best option. We will check it out after the next SeaMonkey release in January.
+* We are looking into doing daily prerelease builds on our infra.
+** Some Linux and macOS builds are now available [https://archive.seamonkey-project.org/nightly/index.html here].
+** Setting up Windows builds takes more time. If soemone needs one plase ask in the SeaMonkey irc channel.
+*** '''frg''' uploads new ones now and then to '''tobins''' [https://seafiles.thereisonlyxul.org/nightly/ new community site].
 <!-- Comment out this section if nothing new fixed
@@ Line 168: / Line 171: @@
 *** 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.
+*** 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.
 * See {{Bug|1688498}} for important current 2.53 issues and enhancement requests.
@@ Line 191: / Line 195: @@
 * 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.
-* comm-central has been updated but needs another round of minor changes WG9s did to build.
+* comm-central has been updated but needs another round of minor changes WG9s did before his death to build.
 * See {{Bug|1452448}} for current comm-central issues. This is not up to date.