I should’ve posted this a few weeks ago when it was relevantish, I started spinning 2.49.3 build 1; but encountered some issues and with a new secfix, I started build 2.
Unfortunately, there might be some delays as our mac is experiencing some issues, which is why I’ve been busy setting up the new infra.
Thank you for your continual patience.
What’s the plans for future versions though? Will Seamonkey continue to use ESRs? That seems like it will drastically impact the heart and soul of what is Seamonkey. Or will Seamonkey continue on from here alone?
I’m more concerned with the simple UI and experience, and would like to be able to use updated extensions, but am afraid Seamonkey will suffer.
Thank you for the updates. 🙂
> What’s the plans for future versions though?
Make it up on the fly 🙂
> Will Seamonkey continue to use ESRs?
Yes. The next planned version is 2.57 based on ESR 60 but it will be delayed. Too much is currently broken and it needs Web Extensions support. Classic extensions will still be supported but with all the apis already removed not many will work without modifications.
> That seems like it will drastically impact the heart and soul of what is Seamonkey. Or will Seamonkey continue on from here alone?
We will not be able to do this alone. Too few devs and people doing support tasks. Not sure what will happen after 2.57. Mozilla effectively destroys the old Gecko source and XUL support in record time now.