SeaMonkey/StatusMeetings/2019-10-13: Difference between revisions

Jump to navigation Jump to search
status meeting notes
(status meeting notes)
 
Line 7: Line 7:
* Location: [irc://chat.freenode.net/seamonkey #seamonkey IRC channel] ''' now on Freenode! '''
* Location: [irc://chat.freenode.net/seamonkey #seamonkey IRC channel] ''' now on Freenode! '''
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):  
* Participants (in order of appearance): frg WG9s IanN rsx11m


== 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'''
** '''WG9s Build Champion'''


=== Action Items ===
=== Action Items ===
Line 22: Line 22:
** We will be on moznet irc too until it is turned off (planned for February 2020).
** We will be on moznet irc too until it is turned off (planned for February 2020).
'''NEW'''
'''NEW'''
* We have a new Sponsor. The announcement and website changes are done in {{bug|1588292}}.
* —
* —
'''OPEN'''
'''OPEN'''
* [http://forums.mozillazine.org/index.php mozillaZine] might close. Frank Lion set up a forum at [https://seamonkey.boards.net/ SeaMonkey Board] for SeaMonkey support issues and discussion.
* [http://forums.mozillazine.org/index.php mozillaZine] might close. Frank Lion set up a forum at [https://seamonkey.boards.net/ SeaMonkey Board] for SeaMonkey support issues and discussion.
** '''IanN''' offered to take it over but has not heard back from the owner.
* For future macOS releases we might need an Apple Developer ID and notarization process. See [https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution Notarizing Your App Before Distribution].
* For future macOS releases we might need an Apple Developer ID and notarization process. See [https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution Notarizing Your App Before Distribution].
* The project areas on the website need further updates to reflect the current responsibilities after some long time developers and maintainers left the project. {{bug|1356106}} has already been filed.
* The project areas on the website need further updates to reflect the current responsibilities after some long time developers and maintainers left the project. {{bug|1356106}} has already been filed.
Line 37: Line 39:
** '''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).
** '''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).
'''CLOSED'''
'''CLOSED'''
* https://www.seamonkey-project.org/ certificate expired on September 12, 2019 — {{Bug|1580858}}.
* We are planning to provide official repos on gitlab.
** An internal meeting is scheduled for Tuesday where we will discuss the first steps.
** Plans have not been finalized yet but the repos will probably be read-only and periodically synced with the offical mercurial repos.
** We need at least 2.53 and 2.57 repos.
** Patches will still be done via bugzilla first and then checked into hg.
** Mozilla does this to a degree. See [https://github.com/mozilla/gecko-dev/ Mozilla gecko-dev repo] as an example.
** Gitlab was choosen because it actually works with SeaMonkey out of the box and the current developer nicks were not taken.
*** Github needs a user override and is not very friendly to unknown or browsers it does not want to support. SeaMonkey users might not be able to use it in the near future at all.
** With git we would be able to integrate gitlab into our infrastructure.
* —
* —


Line 132: Line 124:
** SeaMonkey 2.49.5 is likely the final minor release from comm-esr52, followed by 2.53.1.
** SeaMonkey 2.49.5 is likely the final minor release from comm-esr52, followed by 2.53.1.
** The upcoming macOS 10.15 might cause problems with 2.49.5. {{Bug|1556734}} tracks known problems with Firefox. We advise users not to upgrade now. Fixes will be provided with the upcoming 2.53 version.
** The upcoming macOS 10.15 might cause problems with 2.49.5. {{Bug|1556734}} tracks known problems with Firefox. We advise users not to upgrade now. Fixes will be provided with the upcoming 2.53 version.
** '''ewong''' is looking into uploading the missing crash symbols.
*** '''frg''' tested The official 2.49.5 with macOS 10.15 on his mac mini. It works fine for him but another user on irc reported an unspecified problem. Until the fog clears the update warning stays.
** '''ewong''' uploadad crash symbols. Some seem to be missing.
** '''IanN''' checks the crash stats and sees if he can identify or fix some of them.
** Some minor release issues with the readme and checksums are looked into.
** Some minor release issues with the readme and checksums are looked into.
** clang 8, gcc 7 and 8 are not usable for building 2.49.5 on Linux or for macOS.
** clang 8, gcc 7 and 8 are not usable for building 2.49.5 on Linux or for macOS.
Line 157: Line 151:
*** The big security problems which were in the public up to 60.9 are fixed.
*** The big security problems which were in the public up to 60.9 are fixed.
*** The current security level as of today is more or less at 60.4. Goal is to to be on par with latest ESR 60 soon.
*** The current security level as of today is more or less at 60.4. Goal is to to be on par with latest ESR 60 soon.
*** ICU60, Skia m66, NSS 3.40.1, NSPR 4.20 and so TLS 1.3 have been backported.
*** ICU60, Skia m66, NSS 3.46.1, NSPR 4.22 and TLS 1.3 have been backported.
** Compiler support is more or less up to date
** Compiler support is up to date
*** clang 8, gcc 5, gcc 6, gcc 7 and 8 (one outstanding issue) can be used to build 2.53.1 on Linux or for macOS.
*** clang 7 or 8, gcc 5, gcc 6, gcc 7 and 8 can be used to build 2.53.1 on Linux or for macOS.
*** clang 8, VS2017 and VS2019 are supported under Windows. VS2015 is no longer supported.
*** clang 7 or 8, VS2017 and VS2019 are supported under Windows. VS2015 is no longer supported.
*** clang 9 and gcc 9 support is being looked into.
*** clang 9 and gcc 9 support is being looked into.
** Bill posts the patch files from '''frg''' containing the backported source and fixes on [http://www.wg9s.com/comm-253/ his wg9s website] for 2.53.
** Bill posts the patch files from '''frg''' containing the backported source and fixes on [http://www.wg9s.com/comm-253/ his wg9s website] for 2.53.
Line 166: Line 160:
*** Public official gitlab repos are currently being set up.
*** Public official gitlab repos are currently being set up.
** '''frg''' will do a preliminary 2.53 landing page for the website.
** '''frg''' will do a preliminary 2.53 landing page for the website.
** The safebrowsing V4 api and list fetches are working in 2.53 and up.
** '''IanN''' will look into including My and pt-BR locales. '''frg''' can create patches based on l10n-release and l10n-central suite but these would need to be manually fixed by the translators and checked into a comm-release branch. We did this with nb-NO in {{bug|1391174}}.
** '''IanN''' will look into including My and pt-BR locales. '''frg''' can create patches based on l10n-release and l10n-central suite but these would need to be manually fixed by the translators and checked into a comm-release branch. We did this with nb-NO in {{bug|1391174}}.
** WebExtentions dictionary support should be enabled as soon as possible in 2.53.
** WebExtentions dictionary support should be enabled as soon as possible in 2.53.
** '''IanN''' reports that the internal devtools inspector works for chrome content in SeaMonkey. Please test and report your findings.
** '''IanN''' reports that the internal devtools inspector works for chrome content in SeaMonkey. Please test and report your findings.
** 2.53.1 has been updated extensively in the last 2 weeks. Please test the unofficial release and report any problems with it. All enhancements and fixes for the suite part go into 2.57 and up too.


* SeaMonkey 2.57 Gecko 60 in comm-esr60.
* SeaMonkey 2.57 Gecko 60 in comm-esr60.
Line 230: Line 224:
*** While packed directly it is still maintained as an extension
*** While packed directly it is still maintained as an extension
** Add-ons need to switch to optionsType 3 for 2.57. TB did a fix showing the preferences in the menu list. We need to port this bug for 2.57.
** Add-ons need to switch to optionsType 3 for 2.57. TB did a fix showing the preferences in the menu list. We need to port this bug for 2.57.
* Thunderbird plans to discontinue classic add-ons with the next ESR78 based release.
** Enigmail will be discontinued.
** OpenPGP will be integrated. This is tracked in {{bug|22687}}.
** Lightnig will be fully integrated by then.


* cZ and DOMi should be integrated into SeaMonkey because of the l10n problem tracked in {{bug|1231349}}.
* cZ and DOMi should be integrated into SeaMonkey because of the l10n problem tracked in {{bug|1231349}}.
719

edits

Navigation menu