As per current plan, we'll end up on 52 ESR either way (which is where 2.49.x will come from) to ensure a more regular release cycle and to shield from recent (and future, at least for that year) developments on trunk like disabling non-Flash plugins and EOL for WinXP/Vista.

So, the only question is if it's 2.46 > 2.48 > 2.49.1 or 2.46 > 2.49.0 > 2.49.1 for the next releases.

Not much news here: All remaining patches for the 2.48 release as such should have landed on the release branch now, still fighting with the Mozilla build system and possibly (likely) no automated updates for 2.46 > 2.48 ...

rsx11m wrote:As per current plan, we'll end up on 52 ESR either way (which is where 2.49.x will come from) to ensure a more regular release cycle and to shield from recent (and future, at least for that year) developments on trunk like disabling non-Flash plugins and EOL for WinXP/Vista.

So, the only question is if it's 2.46 > 2.48 > 2.49.1 or 2.46 > 2.49.0 > 2.49.1 for the next releases.

rsx11m,

Well, since May I have been using the akalla 2.49.1 version with zero problems. (User agent: Mozilla/5.0 (Windows NT 10.0; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 Build identifier: 20170528085107)

So whenever they are able to release a final, official version, I think we will have a good browser going forward for at least the next year.

rsx11m wrote:Ok, bad call maybe, I just saw a lot of "Firefox" in these posts which prompted the "split" finger...

I have no idea what is going on here. What is this "split" business? Now I am more confused.

Is this "Seamonkey", "Firefox", both, neither ("core"?)?

I think I am just going to stay with what I have (Firefox 32 bit 54 "beta", Seamonkey 32 bit 2.46 "release") for another month, and see if anything updates/changes itself then, both for Firefox and Seamonkey.

DN123ABC wrote:I have no idea what is going on here. What is this "split" business? Now I am more confused.

When a subtopic emerges in a thread (here: 32/64-bit migration in general, not related to SM nightly builds as the main topic), moderators can split off that subthread into it's own thread. This is done to keep the original thread on topic, but also to make the subthread more visible to others, thus to avoid hiding it.

Is this "Seamonkey", "Firefox", both, neither ("core"?)?

Good question - the SeaMonkey Builds forum is obviously about SM pre-release builds, Firefox forums are about Firefox. There is no dedicated forum for Core issues, though this code is mostly maintained by Firefox devs. We can move the other thread back into SeaMonkey "territory", no problem, whatever fits best.