MozillaWiki

SeaMonkey/StatusMeetings/2020-05-03: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2020-05-03 (view source)

Revision as of 13:14, 4 May 2020

497 bytes added ,  4 May 2020
status meeting notes
(status meeting notes)
 
Line 7: Line 7:
* Location: [irc://chat.freenode.net/seamonkey #seamonkey IRC channel] on Freenode
* Location: [irc://chat.freenode.net/seamonkey #seamonkey IRC channel] on Freenode
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]
* Participants (in order of appearance):  
* Participants (in order of appearance): IanN njsg tonymec teruna frg 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 for keeping comm-central building and ewong for the release upload'''


=== Action Items ===
=== Action Items ===
Line 22: Line 22:


'''OPEN'''
'''OPEN'''
* [http://forums.mozillazine.org/index.php mozillaZine] might close.
** '''IanN''' offered to take mozillaZine over but has not heard back from the owner.
** Frank Lion set up a forum at [https://seamonkey.boards.net/ SeaMonkey Board] for SeaMonkey support issues and discussion.
** mozillaZine user "Wish You Were Here" has set up a phpBB forum at [https://seamonkey.central-us.net/index.php SeaMonkey Usergroup].
** No progress or reply in the last three months. Forum and knowledge base are still functional.
* 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.
* Planning the future of SeaMonkey with a new infrastructure is in progress.
* We want to create a gitlab patch/fixes repo for classic XUL extensions.
** '''IanN''' is looking into it.
'''CLOSED'''
* No movement and seems mozillaZine stays open so close for now.
** [http://forums.mozillazine.org/index.php mozillaZine] might close.
*** '''IanN''' offered to take mozillaZine over but has not heard back from the owner.
*** Frank Lion set up a forum at [https://seamonkey.boards.net/ SeaMonkey Board] for SeaMonkey support issues and discussion.
*** mozillaZine user "Wish You Were Here" has set up a phpBB forum at [https://seamonkey.central-us.net/index.php SeaMonkey Usergroup].
*** No progress or reply in the last three months. Forum and knowledge base are still functional.
* Planning the future of SeaMonkey with a new infrastructure is in progress. Remaining issues will be reported the infrastructure section.
** The documentation on the website needs to be updated for recent build config changes. '''frg''' can support anyone who wants to do this.
** The documentation on the website needs to be updated for recent build config changes. '''frg''' can support anyone who wants to do this.
*** This includes outdated links and other content in the [https://www.seamonkey-project.org/dev/ SeaMonkey Development Resources page].
*** This includes outdated links and other content in the [https://www.seamonkey-project.org/dev/ SeaMonkey Development Resources page].
Line 38: Line 41:
** '''ewong''' will look into it. It might be useful in the future to save us money. Currently we first set up Jenkins.
** '''ewong''' will look into it. It might be useful in the future to save us money. Currently we first set up Jenkins.
** '''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).
* We want to create a gitlab patch/fixes repo for classic XUL extensions.
 
** '''IanN''' is looking into it.
'''CLOSED'''
* —
* —


Line 46: Line 47:
<!--Please update accordingly-->
<!--Please update accordingly-->
* We are building up a new infrastructure using Azure.
* We are building up a new infrastructure 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).
** Jenkins is being set up on the builders.
** Jenkins is being set up on the builders.
*** '''ewong''' is making progress setting up automated build jobs. This will still take some time.
*** '''ewong''' is making progress setting up automated build jobs. This will still take some time.
Line 71: Line 73:
** Website updates from the source are now done via Jenkins.
** Website updates from the source are now done via Jenkins.
* We are looking at l10n tools.
* We are looking at l10n tools.
* 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].
<!-- Comment out this section if nothing new fixed -->
<!-- Comment out this section if nothing new fixed -->
<!-- uncomment if no new stuff comes up -->
<!-- uncomment if no new stuff comes up -->
Line 86: Line 89:
** Do not try to use the comm-central release.
** Do not try to use the comm-central release.
** The installer still works...
** The installer still works...
** l10n is broken in comm-central because of search plugin issues. If we switch to search/list.json then we need to keep the l10n searchplugin xml files for esr60 or switch esr60 too.
** l10n is broken in comm-central because of search plugin issues.
*** Fix for {{Bug|1300198}} will unbreak the comm-central l10n builds.
*** The fixes in {{Bug|1300198}} will unbreak the comm-central l10n builds.
** RDF has been completely removed now.
** RDF has been completely removed now.
** XBL has been completely removed now.
** XBL has been completely removed now.
Line 102: Line 105:
** Do not use any current comm-release based release.
** Do not use any current comm-release based release.
** An updated unofficial 2.53.3 is available from [http://www.wg9s.com/comm-253/ WG9's website]. We accept filing bugs against it.
** An updated unofficial 2.53.3 is available from [http://www.wg9s.com/comm-253/ WG9's website]. We accept filing bugs against it.
** For building please apply the patches from Bills website to the noted comm-release and mozilla-release changeset.
** For building please apply the patches from Bills website to the noted comm-release and mozilla-release changeset.
** If you want to build the latest release without pending fixes you can also check out from [https://gitlab.com/seamonkey-project/ gitlab].
** stylo and webrender building is currently broken but disabled by default.
** stylo and webrender building is currently broken but disabled by default.
** For building please stay at Rust 1.37 for now under Windows.
** For building please stay at Rust 1.37 for now under Windows.
Line 126: Line 131:
<!-- Close comment if new stuff comes up -->
<!-- Close comment if new stuff comes up -->
=== Fixed Source Tree Stuff Since Last Meeting ===
=== Fixed Source Tree Stuff Since Last Meeting ===
* Build breakage in comm-central was adressed and fixed.
* &mdash;
* &mdash;
<!-- Open comment if no new stuff comes up -->
<!-- Open comment if no new stuff comes up -->
Line 132: Line 136:
=== Release Train ===
=== Release Train ===
* SeaMonkey 2.53.x / Gecko 56 in our gitlab comm-release repo.
* SeaMonkey 2.53.x / Gecko 56 in our gitlab comm-release repo.
** The 2.53.1 final was released on February 28th
** The 2.53.2 final was released on May 3rd.
*** The sources can be checked out from the 2_53_1_final branch in the [https://gitlab.com/seamonkey-project gitlab project repos].
*** The sources can be checked out from the 2_53_2_final branch in the [https://gitlab.com/seamonkey-project gitlab project repos].
** 2.53.2 beta 1 was released on April 15th
** '''2.53.2 final is scheduled to be release next week!'''
*** The 2.53.2 final release is tracked in {{Bug|1631538}}.
*** The 2.53.2 final release is tracked in {{Bug|1631538}}.
*** The language packs will be re-released soon because of a minor problem during upgrade.
*** The release notes and website update are tracked in {{Bug|1631539}}.
*** The release notes and website update are tracked in {{Bug|1631539}}.
**** Thanks to all the official and inofficial localizers for the good work.
*** We pan to release 2.53.3 beta 1 at the end of May.
*** Thanks to all the official and inofficial localizers for the good work.
*** NSS 3.49 and up drop the dbm compatibility module. This has been restored for 2.53.2. Later we might do a hard block upgrading from an older release.
*** NSS 3.49 and up drop the dbm compatibility module. This has been restored for 2.53.2. Later we might do a hard block upgrading from an older release.
**** Distributions using the system nss might need to adjust compile settings for this.
**** Distributions using the system nss might need to adjust compile settings for this.
Line 153: Line 155:
** A meta bug {{Bug|1584728}} tracks the rdf removal from SeaMonkey.
** A meta bug {{Bug|1584728}} tracks the rdf removal from SeaMonkey.
** Security fixes are backported frequently. '''frg''' tries to keep it as current as possible in his spare time.
** Security fixes are backported frequently. '''frg''' tries to keep it as current as possible in his spare time.
*** The big security problems which were in the public up to 74.0 are fixed.
*** The big security problems which were in the public up to 74.0.1 are fixed.
*** The current security level as of today is more or less at 60.6. Goal is to to be on par with latest ESR 60 soon and then move up.
*** The current security level as of today is more or less at 60.8. Goal is to to be on par with latest ESR 60 and then move up.
*** ICU60, Skia m66, sqlite 3.31.1 NSS 3.50, NSPR 4.25 and TLS 1.3 have been backported for 2.53.2.
*** ICU60, Skia m66, sqlite 3.31.1 NSS 3.51, NSPR 4.25 and TLS 1.3 have been backported for 2.53.3.
** Compiler support is up to date.
** Compiler support is up to date.
*** clang 5, 7 or 8, gcc 6.1, gcc 7 and 8 can be used to build 2.53.1 on Linux or for macOS. Support for gcc 5.x and 4.x has been removed.
*** clang 5, 7 or 8, gcc 6.1, gcc 7 and 8 can be used to build 2.53.2 on Linux or for macOS. Support for gcc 5.x and 4.x has been removed.
*** clang 7, 8 or 9, VS2017 15.9.13 and VS2019 are supported under Windows. Support for VS2015 and earlier VS2017 versions has been removed.
*** clang 7, 8 or 9, VS2017 15.9.13 and VS2019 are supported under Windows. Support for VS2015 and earlier VS2017 versions has been removed.
*** gcc 9 support is being looked into. Clang 9 support is added to 2.53.3 only. Clang 10 support is being tested soon.
*** gcc 9 support is being looked into. Clang 9 support is added to 2.53.3 only. Clang 10 support is being tested soon.
Line 177: Line 179:
*** The sources are currently marked private in our [https://gitlab.com/seamonkey-project gitlab project repos].
*** The sources are currently marked private in our [https://gitlab.com/seamonkey-project gitlab project repos].
*** An alpha 1 source is being prepared.
*** An alpha 1 source is being prepared.
*** The comm-esr60 repos are closed. All fixes not in them are available from [http://www.wg9s.com/comm-257/ wg9s website] untio the gitlab repo is ready.
*** The comm-esr60 repos are closed. All fixes not in them are available from [http://www.wg9s.com/comm-257/ wg9s website] until the gitlab repo is ready.
*** '''frg''' maintains the patches for 2.57 on gitlab in a private repo. As with 2.53 anyone who wants access can send him an email but Bills repo is usually up to date.
*** '''frg''' maintains the patches for 2.57 on gitlab in a private repo. As with 2.53 anyone who wants access can send him an email but Bills repo is usually up to date.
** Mail and news are still broken in SeaMonkey 2.57.
** Mail and news are still broken in SeaMonkey 2.57.
** Ad and Script Blocker support needs WebExtension support in SeaMonkey 2.57.
** Ad and Script Blocker support needs WebExtension support in SeaMonkey 2.57.
*** Like 2.53 l10n needs to be hand rolled. The strings from 2.53 and comm-central will be used as a base.
*** Like 2.53 l10n needs to be hand rolled. The strings from 2.53 and comm-central will be used as a base.
*** To test l10n building 2.57 is now available in German on [https://www.wg9s.com/comm-257-de/de/ wg9s website].
**** The cZ language pack is no longer compatible because 2.57 switches to webextension language packs. A hack has been put into the de package till this is solved.
*** comm-central only patches must not delete any strings in the suite en-US directory until 2.57 is out.
*** comm-central only patches must not delete any strings in the suite en-US directory until 2.57 is out.
**** For backported changes strings can be deleted.
*** When doing patches please make sure to change the l10n labels when the content changes.
*** When doing patches please make sure to change the l10n labels when the content changes.
*** cZ strings will be copied to suite. This is tracked in {{Bug|1606400}}.
*** cZ strings will be copied to suite. This is tracked in {{Bug|1606400}}.
*** cZ, DOMi, debugQA and the Lightning extension will be compatible with 2.57.
*** cZ, DOMi, debugQA and the Lightning extension will be compatible with 2.57.
*** {{Bug|1231349}} was fixed with a workaround patch by '''ewong'''. This can be used for 2.57 too.
*** {{Bug|1231349}} was fixed with a workaround patch by '''ewong'''. This is used for 2.57 too.
** Thunderbird did switch to WebExtension dictionaries.
** Thunderbird did switch to WebExtension dictionaries.
** We will switch search plugins to a central json file for 2.57. See {{Bug|1300198}}. TB and Fx did this long ago.
** We will switch search plugins to a central json file for 2.57. See {{Bug|1300198}}. TB and Fx did this long ago.
Line 232: Line 237:
*** '''IanN''' is ready to import them into the comm tree. He just needs to decide when and if (esp with DOMi if devtools can be got to work).
*** '''IanN''' is ready to import them into the comm tree. He just needs to decide when and if (esp with DOMi if devtools can be got to work).
** The language pack for cZ will be removed and a translated cZ will be included.
** The language pack for cZ will be removed and a translated cZ will be included.
** '''frg''' has regular l10n repack support almost finished for 2.53 and up.


* Our distributed extensions do not get updated during a new install.
* Our distributed extensions do not get updated during a new install.
Line 238: Line 242:


* WebExtension support in SeaMonkey is tracked in {{Bug|1320556}}. As of now working on this has not started.
* WebExtension support in SeaMonkey is tracked in {{Bug|1320556}}. As of now working on this has not started.
** Support for adding Web extension dictionaries in 2.53 has started.  
** Support for adding Web extension dictionaries in 2.53 has started.
** This would be needed for a ESR60 based SeaMonkey 2.57.
** This would be needed for a ESR60 based SeaMonkey 2.57.


Frg
726

edits

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