647
edits
SeaMonkey/StatusMeetings/2023-11-12: Difference between revisions
SeaMonkey/StatusMeetings/2023-11-12 (view source)
Revision as of 13:11, 3 December 2023
, 3 December 2023status meeting notes
(merge previous meeting notes) |
(status meeting notes) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 13: | Line 13: | ||
== Agenda == | == Agenda == | ||
* Who's taking minutes? -> ''' | * Who's taking minutes? -> '''frg''' | ||
* Nominees for Friends of the Fish Tank: | * Nominees for Friends of the Fish Tank: | ||
** ''' | ** '''Tom Healy and team from mozilla for working with us on extending mozilla infrastructure use''' | ||
=== Action Items === | === Action Items === | ||
| Line 41: | Line 41: | ||
*** '''WG9s''' has set up an archive and we have a solution for prerelease development versions now in place. | *** '''WG9s''' has set up an archive and we have a solution for prerelease development versions now in place. | ||
*** We got a preliminary approval note to extend our stay on the other mozilla infrastructore 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 infrastructore till the end of 2024 but need to formalize some things till then. | ||
*** '''ewong''' already has copied the release files and we will host them on azure. | |||
'''CLOSED''' | '''CLOSED''' | ||
| Line 129: | Line 130: | ||
*** clang 16 and hight might work but have not been tested yet. | *** 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 | ** clang 7 to 17, VS2017 15.9.13+ and VS2019 are supported under Windows x64. | ||
** VS2019 and VS2022 are currently not supported for compiling Windows x86. | ** VS2019 and VS2022 are currently not supported for compiling Windows x86. | ||
** 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. | ||
| Line 170: | Line 170: | ||
** This does not affect 2.53 builds which use back merged strings from the upstream l10n repos. | ** This does not affect 2.53 builds which use back merged strings from the upstream l10n repos. | ||
** Patches for build breakage and new reviewed functionality in suite have been checked in. | ** Patches for build breakage and new reviewed functionality in suite have been checked in. | ||
** mozilla plans to move to github. We expect MZLA to follow and need to evalutate later how central source updates can be done. | |||
<!-- Comment out this section if nothing new fixed --> | <!-- Comment out this section if nothing new fixed --> | ||
| Line 373: | Line 374: | ||
==== ewong ==== | ==== ewong ==== | ||
==== frg ==== | ==== frg ==== | ||
Mostly did work | Mostly did work in the last 3 weeks to get 2.53.18b1 out the door. Paid work and life took over again so not much done wrt web compatibility. | ||
Waiting for review: | Waiting for review: | ||
| Line 385: | Line 386: | ||
Reviewing: | Reviewing: | ||
* Changes from '''IanN''' | * Changes from '''IanN'''. | ||
Working on: | Working on: | ||
* Backporting {{Bug|1634135}} Enable new regexp engine. Waterfox Classic did it some time ago but our codebase is a bit different in parts here. | * Backporting {{Bug|1634135}} Enable new regexp engine. Waterfox Classic did it some time ago but our codebase is a bit different in parts here. | ||
** This took too long and preliminary patch from ''buc''' is now in. This needs occasional rebasing but too much sites broke lately because of the missing regexp support. | ** This took too long and preliminary patch from ''buc''' is now in. This needs occasional rebasing but too much sites broke lately because of the missing regexp support. | ||
** Further cleanup done with the SpiderMonkey changes but now causes crashes during GC so not ready for prime time. | ** Further cleanup done with the SpiderMonkey changes but now causes crashes during GC so not ready for prime time. | ||
** Working on a parallel branch to update SpiderMonkey for this and other stuff. | |||
* {{Bug|1296850}} Show standard loading indicator images in tab when busy or progress attribute are set. Asked someone who wants to help out to look at the icons. Got the icons but have no time at the moment. | * {{Bug|1296850}} Show standard loading indicator images in tab when busy or progress attribute are set. Asked someone who wants to help out to look at the icons. Got the icons but have no time at the moment. | ||
* Bringing ICU and tzdata up to the current level for 2.53. Some progress with alignment of the intl code. Now at ICU 64.2. | * Bringing ICU and tzdata up to the current level for 2.53. Some progress with alignment of the intl code. Now at ICU 64.2. | ||
* RDF removal with '''IanN''' for 2.53 and up. Full removal for 2.53 will only happen if it does not break critical or too many add-ons. | * RDF removal with '''IanN''' for 2.53 and up. Full removal for 2.53 will only happen if it does not break critical or too many add-ons. | ||
| Line 400: | Line 401: | ||
Not working on: | Not working on: | ||
* Fixing comm-central. Not worth it currently. Only see that it builds. | * Fixing comm-central. Not worth it currently. Only see that it builds. With more backports we are slowly fixing central issues too. | ||
Shelved for later: | Shelved for later: | ||
| Line 407: | Line 408: | ||
Titbits: | Titbits: | ||
* | * 2.53.18b1 was done this week and should be released soon. | ||
==== IanN ==== | ==== IanN ==== | ||
Mainly doing backports. | |||
Checked in for website: | |||
* Nothing this time around | |||
Checked in for 2.53.18+ / comm-central: | |||
* {{Bug|1859386}} Initialize the toolkit l10n resource sources for L10nRegistry | |||
Waiting for checkin: | |||
* {{Bug|1611010}} Remove needless implements='nsIDOMEventListener' and QI | |||
* {{Bug|1614671}} Port |{{Bug|1456035}} - Add native QueryInterface helper with fast path for XPCWrappedJS| to SeaMonkey | |||
* {{Bug|1642188}} Port |{{Bug|1455052}} part 12 - Remove JS uses of nsIDOMEvent| to SeaMonkey | |||
Waiting for review: | |||
* {{Bug|1645892}} Port changes to SSLStatus interfaces to SeaMonkey | |||
* {{Bug|1646495}} Stop using nsIDocShell::forcedCharset in SeaMonkey | |||
* {{Bug|1687385}} Update SeaMonkey mozconfigs | |||
* {{Bug|1864287}} Use punycode in SeaMonkey JS | |||
Waiting for feedback: | |||
* Nothing this time. | |||
Working on: | |||
* {{Bug|1633729}} Update about:buildconfig to display comm as well as mozilla source information - comm-central part | |||
* {{Bug|1616034}} Update SessionStore code for SeaMonkey | |||
* {{Bug|1612386}} Don't always update lastRelatedTab information when browser.tabs.insertAllTabsAfterCurrent is true | |||
* {{Bug|1577372}} Working copy functionality was removed from page info window | |||
* {{Bug|1573595}} [meta]Update pageInfo files | |||
* {{Bug|1578061}} [meta]Update SeaMonkey's context menu | |||
* {{Bug|1581176}} [meta]Update SeaMonkey's certificate / net error handling UI | |||
* {{Bug|1579640}} Fix access key clashes in prefs | |||
* {{Bug|657604}} Remove the RDF global object. (Port {{Bug|437869}} to SeaMonkey.) | |||
* {{Bug|1380613}} sessionrestore will not restore anything if another tab is open | |||
* Backporting changes needed for build system | |||
Back burner: | |||
* {{Bug|1501790}} Port changes from {{Bug|1458314}}, {{Bug|1506915}}, and {{Bug|1458308}} to SeaMonkey | |||
* {{Bug|1542608}} Port |{{Bug|394984}} Unable to update on mac if admin user is not the same admin user as the person who installed firefox| to SeaMonkey | |||
==== njsg ==== | ==== njsg ==== | ||
==== Rainer Bielefeld ==== | ==== Rainer Bielefeld ==== | ||
| Line 424: | Line 464: | ||
* We decided to switch the meeting schedule to a 3 week interval. If the date is a holiday it will be moved up a week and then goes back to 3 weeks. | * We decided to switch the meeting schedule to a 3 week interval. If the date is a holiday it will be moved up a week and then goes back to 3 weeks. | ||
** Should business be booming again we will probably move back to the old schedule. For now not enough traffic to justify the two week schedule. | ** Should business be booming again we will probably move back to the old schedule. For now not enough traffic to justify the two week schedule. | ||
* The next meeting will be held in three weeks on Sunday December | * The next meeting will be held in three weeks on Sunday December 3rd, 2023, 15:00 UTC (16:00 CET). | ||
* — | * — | ||