There, Phoebus Account Registration and Verification is done.. If anyone cares.

sup Mc

Happy Sunday Mc therube

:-)

hi, I checked the blog the other day... have the plans for the future cleared up a bit since the half of December?

hrosik No we are still working on getting the next minor version out. This will be 2.49.5 Planned major is still 2.57

frg_away: 2.57 based on FF57?

ESR60

wow!

looking further - fork latest working codebase or replicate SM functionality in XHTML/JS?

I wish I know. Probably the end of the line unless more devs pop up.

Meeting in 23 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2019-01-20

(22)

(23)

Meeting in 10 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2019-01-20

Meeting in 4 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2019-01-20

Meeting time - wiki.mozilla.org/SeaMonkey/StatusMeetings/2019-01-20

Who's taking minutes?

Me

thanks frg

Nominees for Friends of the Fish Tank?

wait a minute to see if the others pop up?

!summon rsx11m

IanN: Error: "summon" is not a valid command.

Hi rsx11m

see it worked, silly foxbot

hi rsx11m

hi ewong

Hi ewong

hi IanN, frg

hi frg IanN ewong foxbot

!knight frg

IanN: Error: "knight" is not a valid command.

anyway, Nominees for Friends of the Fish Tank?

hi rsx11m

ewong for the initial infra.

frg: it's not 100% up and running.. so that nomination is a bit premature

ewong: for his magic with kallithea

ewong I don't care. It is a huge task and not the end of the way :)

seconded

Action Items

wb Mc

Hi Mc

hi all

I've started doing some updates to the website, but doing in small chunks so I, hopefully, won't break anything

I did think whether we could somehow switch to the way TB and Firefox do websites, but not sure where to start with that

Saw it. We should remove the mozilla logo from the first page too. And more of the links.

IanN, Frg, try the buildbot again

TB and Fx pages are a whole new ballgame I think. Multilingual.

frg: yeah, not high on the list but something for the future

anything on action items?

still looking to update contirbutors etc.

yeah, lots to do

Status of the SeaMonkey Infrastructure

frg: I've added us to bug 1515507

Bug bugzilla.mozilla.org/1515507 normal, --, ---, iann_bugzilla, ASSIGNED , Update SM Web Site to include references to SM EV

rsx11m saw it. Thanks

I better work on that then...

8-)

new infra's being worked on

trying to iron out some wrinkles to allow 2.49.5 release

Well me too.

bug 1521254 looks weird...

Bug bugzilla.mozilla.org/1521254 critical, --, ---, nobody, NEW , EOF occurred in violation of protocol (_ssl.c:661)

yeah :(

and bug 1521258

Bug bugzilla.mozilla.org/1521258 normal, --, ---, nobody, NEW , getting rust backtrace while building c-c linux64 nightly

Mercurial issue with recent versions?

the first is driving me nuts... I'm thinking of reboothing the master

ewong: what mercurial version is it on?

version 4.5.3

Seems to be a common problem:

ewong: does a new clone work (into a different location)?

IanN: no.. can't even clone anything

ewong: strange, I've just cloned with 4.5.3 locally and it works

no.. it's the master.. going through what frg linked and see if something comes up

pretty old probably no relevant and different problem.

looks like a collection of multiple issues exposed with the requests package

(which hg doesn't seem to be using)

ewong: what version of openssl is installed?

mozbuild is now at 4.8.1 I am still using Tortoise 4.6.1 Later thg versions seem to use memory aplenty with queue patches. Not sure if it is a bug.

also, the reference to PyOpenSSL may be helpful to check (?)

the problem is, it *used* to work.. it only started futzing sometime ago..

anyway, Status of the SeaMonkey Source Tree

It builds thanks to Bill. Need to remember him for the next FotFT :)

All patches for 2.49.5 are in. I will do further backports when we start building.

thumbs up!

Backporting becomes harder and harder with 52. 56 now has most of the preliminaries in but I won't do this with 52.

mail structure has been more or less aligned with TB so porting should be easier.

or lets say more straightforward.

frg: straight forward is good :)

xul tree is being removed piecemeal. Still see no future beyond 2.57. Maybe TB can keep up so that we have a chance later if we want.

:-/

classic ad-ons will be a goner for sure in 68.

next merge is scheduled for tomorrow, btw.

oh yay...;/

frg: I see that TB have switched to WebExtension dictionaries and are planning to for 60.5 too

within an ESR cycle?

rsx11m can you request the flags then? We are also missing 2.63+ in Version now. Not really needed there because it is usually old or trunk.

frg: I'll do so once they've actually completed the merges, just cloning the bug I'd think

rsx11m yes. We might need to do something about language packs too.

nice :-P

Are we sort of on Release Train now?

And it seems they are ripping out support for non taskcluster. We probably need to switch to a local "alike" build process.

IanN: I'd think so

For release train esr52 updates are in place. M-esr52 tree is closed. Not sure if we need buildbot changes to account for this. Pushes need to have closed tree.

c-esr52 is still open. I usually push to the default banch and then merge to our esr branch.

My pet release 2.53 is now close to a 1000 patches combined :)

anybody complained yet about your hg.mozilla.org/releases/mozilla-esr…/pushloghtml?changeset=6e4ad8a8f2e8 push?

rsx11m: not seen anything

Mapi bug 393302 has been fixed. So a Windows x64 is fully functional now. Put it in 2.53 for testing. Full y fixed in Bills next build.

Bug bugzilla.mozilla.org/393302 major, --, Thunderbird 66.0, mikekaganski, RESOLVED FIXED, Can't "send-to" (MAPI) using Seamonkey and Thunderbird X86_64-bit

rsx11m pushed one bug first to see if I stir the natives and after it did fine put the whole bunch in :D

sure will be good to get 2.49.5 out and keep the community happy ... 8-)

If the mapi fixes stick I will backport to 2.49.x Should be possible.

all sounds good

Extensions and Plugins Compatibility Tracking

Not much new here. Sitll plan to look into DOMi and do final patches for 2.57.

l10n bug still open so we can't build l10m with them.

ok, thanks

2.x, 2.next, Feature List, Planning & Roundtable

nothing from me.

nothing new

or me

any AOB?

nope

laterz .. gotta sleep

Will probably be a bit busy in the next weeks so replies during the week may be late.

ewong|away: gotta have breakfast ;-)

next meeting February 3rd?

(apparently everybody has left already...)

Sounds like a plan

rsx11m: yes, next meeting in 2 weeks

rsx11m no looking at the infra in parallel

ok, see you in 14 days again

bye!

bye

status meeting notes are up. Rather short but everything is progressing at last :)

frg_away: what is the differnce fighting with mozilla-central changes between SM and TB?

hrosik we have the browser to fix up. And more and more support for non Firefox features is removed. Also bookmarks api has been gutted, full theme and rss support removed and and and. It would probably be a pale shadow of the current SeaMonkey.

frg_away: hmm... how are they actually handling XUL deprecation?

I've been toying with the idea of trying github.com/browserhtml/browserhtml

which could theoretically be a viable option in the long run

servo as a full blown browser is dead.

frg_away: it is?

well, it actually doesn't matter whether it's going to be Servo or Gecko with parts from Servo

hrosik Gecko will be construction site for years if it survives and that I doubt. You can do a small project with volunteers but not something that big. Someone might pull the plug in the future and then it becomes interesting :)

frg_away: what would be the reasons for not surviving? financial implosion of MoCo?

market share is down and still does. Kept afloat by google money mostly. Financials are currently ok. They already try to invest in other things like pocket and sponsored advertizing ehh I mean helpful suggestions. I don't know what will happen but I have a hunch. If I am right or wrong it won't help SeaMonkey.

from my pov, that breaking of codebase would have to be really profound to kill it - given how it survived 3 (or 4?) changes in add-on intrerfaces

but I guess it could marginalize Gecko to under 5%

funny thing how Google killed the web...