MozillaZine

SM Nightly Build January 2017

Discussion about Seamonkey builds
rsx11m
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted March 5th, 2017, 10:42 am

DN123ABC wrote:2 to 3 weeks have passed. Where is this "beta"? Would it be 2.48 beta, 2.49 beta, or something else?

SeaMonkey 2.48 beta 1 has been tagged but currently fails on Linux due to GTK issues, needing the fix to land on the mozilla-beta side (approval requests are still pending).

Next release might be 2.48 final or going straight to 2.49, whatever is easier.

ndebord

User avatar
 
Posts: 721
Joined: December 7th, 2002, 9:53 am

Post Posted March 6th, 2017, 5:00 pm

rsx11m wrote:
DN123ABC wrote:2 to 3 weeks have passed. Where is this "beta"? Would it be 2.48 beta, 2.49 beta, or something else?

SeaMonkey 2.48 beta 1 has been tagged but currently fails on Linux due to GTK issues, needing the fix to land on the mozilla-beta side (approval requests are still pending).

Next release might be 2.48 final or going straight to 2.49, whatever is easier.


rsx11m


My preference would be to go straight to 2.49 ESR, so we can at the very least enjoy SM for another year or so.

Just saying.
-N-

Windows 10 Home, PandaFREE, MalwareBytesPro and Scotty is on Patrol
Dulce bellum inexpertis

rsx11m
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted March 9th, 2017, 6:35 pm

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
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted June 14th, 2017, 5:13 pm

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 ...

ndebord

User avatar
 
Posts: 721
Joined: December 7th, 2002, 9:53 am

Post Posted June 17th, 2017, 2:10 pm

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.
-N-

Windows 10 Home, PandaFREE, MalwareBytesPro and Scotty is on Patrol
Dulce bellum inexpertis

rsx11m
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted June 19th, 2017, 12:48 pm

DN123ABC wrote:Still on 2.46 here. What about 64 bit builds?


I've split this discussion off to viewtopic.php?f=7&t=3031202 in Firefox General given that it's (a) about Firefox and (b) off-topic here.

DN123ABC
 
Posts: 149
Joined: January 9th, 2017, 10:10 am

Post Posted June 19th, 2017, 1:49 pm

I thought it was about "Seamonkey".

I included Firefox as well, but was primarily asking about "Seamonkey".

??

rsx11m
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted June 20th, 2017, 9:28 am

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

DN123ABC
 
Posts: 149
Joined: January 9th, 2017, 10:10 am

Post Posted June 20th, 2017, 9:39 am

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.

rsx11m
Moderator
 
Posts: 14406
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted June 20th, 2017, 5:32 pm

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.

Return to SeaMonkey Builds


Who is online

Users browsing this forum: No registered users and 1 guest