12:17:25 Hi tonymec|away 12:18:46 hi frg_Away 14:36:13 status meeting in 27 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2023-11-12 14:56:57 status meeting in 7 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2023-11-12 15:01:59 hi .* 15:03:15 status meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2023-11-12 15:03:34 Hi rsx11m all 15:03:42 hi frg IanN 15:04:34 hi rsx11m 15:04:59 Who's taking minutes? 15:05:19 me 15:05:48 thanks 15:05:57 Nominees for Friends of the Fish Tank? 15:06:29 Tom healy and team from mozilla for workign with us on infrastructure "time extension" 15:07:00 seconded 15:07:18 thirded 15:08:34 Action Items 15:09:26 we got a preliminary approval to continue using mozilla infra till the end of 2024 but need to work out some details with MZLA 15:09:50 distribution is still on track to swithc to our own server whereever this is :) 15:10:58 ewong is working on that part 15:11:11 yes he stated that he is on track with it. 15:11:13 yo~ 15:11:18 hello world~ 15:11:24 hi tomman 15:11:38 Hi tomman 15:12:00 Status of the SeaMonkey Infrastructure 15:12:35 The soon to be releases 2.53.18b1 will switch to BugSplat for crash reporting. 15:13:52 IanN should we ask ewong to turn off our server with 2.53.18 final? 15:15:43 frg: well we can schedule for after it is released 15:18:44 Status of the SeaMonkey Source Tree 15:19:43 All building. Still backporting js stuff with Myckel in a parallel branch. Now and import.meta and BigInt but need to check soon fi this even compiles :) 15:20:05 ah, the new duo of destruction 15:20:53 tomman well I got it working till end of 61a1 already but the new regexp stuff did crash. So putting more in. 15:21:17 and I am working on other backports 15:21:44 Still want to unbreak stylo too but this is urgkkk.... 15:22:05 currently mutator or mutalator or something like that 15:22:28 uri mutator but not the removal parts 15:23:24 Yesterdays cZ is broken becuase of it. Should be fixed with current morning build from WG9s 15:24:05 Release Train 15:24:51 2.53.18b1 is done and should be out in the next few days. Please test. This should be very stable. 15:26:16 Hi WG9s 15:26:26 Hi 15:26:28 hi WG9s too 15:26:56 2.53.18 has the new regexp stuff in which should help with tons of websites. 15:27:03 Hopefully final will be out early December 15:27:58 For updates we need to find a solution switching to a different update url afterwards. 15:29:13 Oh maybe not app.update.url already pointing to our server. 15:30:10 frg: yeah, that's already sorted 15:32:29 Extensions Tracking 15:33:42 bau. Still not trying to introduce new breakage :) 15:34:02 we do try 15:34:50 as long as you aren't successful with that ;-) 15:35:22 Move Fast And Break Things! 15:36:40 It needs to happen now and then but hopefully the worst is over. There are some compartment to realm changes in later js fixes. I hope this does not affect add-ons 15:37:05 ditto 15:37:08 We also started with fluent translations. This could end up bad too :) 15:38:56 2.Next, Feature List, Planning & Roundtable 15:39:59 IanN is moving fast today 8-) 15:40:06 bau but mozilla is switching from Mercurial to git. Might affect us upstream. Not happy about it. Mercurial is so much better when it comes to patch management. 15:40:33 frg: yeah, agreed but I saw that coming 15:41:05 kids can't live without Giggityhub nowadays :/ 15:41:16 it's basically the only thing they know, and Mozilla knows this 15:41:48 hope they are at least providing decent instructions ... 15:42:26 ... like "don't rebase the master branch" etc. 15:42:32 I think the only announcement I saw so far was about Firefox, so will it affect comm-central? or is the switch just for mozilla-central? 15:42:46 They move to github. Might affect checkin right for comm-central becuase mZLA will follow 100%. 15:43:03 I hate phab and gitbub both. 15:43:25 [my comment on github requires javascript to be rendered] 15:45:02 let's go back to cvs, shall we? :-p 15:45:15 urgh 15:45:29 svn urgk++ 15:45:39 Or maybe Walgreens 15:46:40 I take CA librarian over it but maybe we should continue :) 15:47:47 AOB 15:47:50 Hey still alive :) https://ftpdocs.broadcom.com/cadocs/0/CA%20Librarian%20%204%204-ENU/Bookshelf.html 15:47:58 AOB bau 15:48:30 Big release at work so if I don't shoot myself I will probably be busy in the next two weeks. 15:50:43 urgh broadcom 15:51:22 Yeah they bought all the CA stuff. CA Telon too. Was great then but probably dead now. 15:51:29 thanks for your time today. Next meeting in 3 weeks time, same bat channel, same bat time 15:51:36 cu 15:51:56 December 10th then! 15:52:05 almost done with 2023... 15:52:11 Bye for now 15:52:12 rsx11m: not 3? 15:52:57 argh, you are right ... 15:54:22 corrected, thanks! 15:54:36 my calendar must have been out of sync ;-) 15:54:40 and we may have one on 17th too, as 24th is too Christmasy 15:54:41 December 3th, so... 11:00 VET in my case 15:55:30 IanN: 31st isn't much better, but we can discuss next time 15:56:05 yeah probably 17th then 7th Jan 15:56:15 yes, discussion for next meeting 15:56:38 ^^yepp, my thinking too 15:57:26 or we combine 3rd and 17th into the 10th, then January 7th ;-) 15:58:02 too complicated :P 15:58:27 ok, let's stick with December 3rd 15:00 UTC for now 8-) 15:58:38 yeah, thanks 15:58:46 unless there's some holiday, for december, 17th probably works well, it's probably better to have two meetings (so 3rd plus 17th) rather than one? 15:59:20 (That is, meetings on the 3rd and 17th, not two on the 20th) 16:00:04 I think we'll go with 3rd and 17th now, but can finalize on the 3rd 16:00:24 sorry for adding more confusion... 16:02:14 For January what I fear is that the 7th might have some holiday or feast as well (for me that date is fine, I think) 16:03:35 well, it's the holiday season, so many people travel one day or the other 16:04:03 7th here is fine, it's just one day after start of Epiphany in Hispanic countries 16:04:13 well, assuming you're not in the road, of course 16:04:15 happy Thanksgiving soon, by the way! 16:04:53 for those that do it... 16:05:08 my point, it varies ;-) 16:05:52 when is thanksgiving? 16:06:17 23rd, if my calendar is correct 16:06:23 date: invalid date 'thanksgiving' <-- well, that didn't work 16:06:43 11 days from now 16:08:50 ok, happy whatever-you-celebrate then! 16:08:54 see you next time 16:10:19 c u rsx11m