SeaMonkey/StatusMeetings/2023-10-01: Difference between revisions

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 WG9s CoordinatorTobin rsx11m 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'''
** '''Rainer Bielefeld for help aand website changes'''


=== Action Items ===
=== Action Items ===
Line 35: Line 35:
** We need to find replacements for bugzilla, translations via Pontoon, add-on and the distribution site.
** We need to find replacements for bugzilla, translations via Pontoon, add-on and the distribution site.
*** Reviews for SeaMonkey add-ons seem to no longer be done anyway. We don't have any access there.
*** Reviews for SeaMonkey add-ons seem to no longer be done anyway. We don't have any access there.
** We asked for a meeting with mozilla representatives to work something out.
** 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.
*** 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 plan to move off mozilla.archive.org at the end of the year and set up our own distribution server. '''IanN''' and '''ewong''' will handle this.
*** '''WG9s''' has set up an archive and we have a solution for prerelease development versions now in place.


'''CLOSED'''
'''CLOSED'''
Line 124: Line 126:
* Compiler support is up to date.
* Compiler support is up to date.
** clang 6 to 15, gcc 7.1 to 11 can be used to build on Linux or clang only for macOS.
** clang 6 to 15, gcc 7.1 to 11 can be used to build on Linux or clang only for macOS.
*** clang 15 is currently not supported with macOS builds if you enable crash reporting.
*** clang 15 and higher is currently not supported with macOS builds if you enable crash reporting.
*** clang 16 and hight might work but have not been tested yet.
** 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 15, VS2017 15.9.13+ and VS2019 are supported under Windows x64.
** clang 7 to 16, VS2017 15.9.13+ and VS2019 are supported under Windows x64.
*** clang 17 might work but has not been tested yet.
** VS2019 and VS2022 are currently not supported for compiling Windows x86.
** VS2019 and VS2022 are currently not supported for compiling Windows x86.
** Clang 16 is problematic and might not compile 2.53. Might need more backports.
** 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.
** Support for clang 6 will be removed soon. The new regexp parser needs full c++17 support. Currently we worked around it but while this may work with clang 5 and 6 it is basically untested.
** Support for clang 6 will be removed. The new regexp parser needs full c++17 support. Currently we worked around it but while this may work with clang 5 and 6 it is basically untested.
** 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.
* The latest macOS sdk is now supported in 2.53.15b1 or later.
* The latest macOS sdk is now supported in 2.53.15b1 or later.
647

edits