MozillaZine

SeaMonkey 2.27 will be skipped, 2.26.1 released instead

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

Post Posted May 28th, 2014, 7:45 am

You may have noticed that there hasn't been any 2.27 beta released yet. The short story is that the Gecko 30.0 platform changes require newer system libraries, and hence updates to the builders, especially on Linux (which is still lacking nightly builds due to that reason). This hasn't happened yet.

As a result, it appears likely that the 2.27 release (due in two weeks) will be skipped (meeting minutes, IRC logs). Instead, the current plan is to release a 2.26.1 version (i.e., based on the Gecko 29.0 branch which is not affected by the conflicting changes) which would get selected fixes backported. The next "full" release would be 2.28, assuming that the issues have been resolved by then.

patrickjdempsey

User avatar
 
Posts: 22778
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted May 28th, 2014, 2:36 pm

Hope they get it all running soon!
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

patrickjdempsey

User avatar
 
Posts: 22778
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted May 28th, 2014, 4:22 pm

So I'm guessing this means we will continue to see these "Error: A promise chain failed to handle a rejection." in the Console until SeaMonkey 2.28.

https://bugzilla.mozilla.org/show_bug.cgi?id=969318
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

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

Post Posted May 28th, 2014, 4:35 pm

I don't see any specifics yet how the 2.26.1 release is going to be established. Obviously, patches which landed on what's now comm/mozilla-beta will need to be investigated and approved for that SM-specific release branch in comm/mozilla-release. That should be easier for the comm-beta patches than for the mozilla-beta patches, given that Core is not in direct control of either SeaMonkey or Thunderbird (and Firefox likely doesn't have much interest in solving problems of SeaMonkey). Thus, let's see what's happening over the next two weeks, but a useful first step would certainly be to identify and nominate those candidate fixes for 2.26.1, by whatever mechanism can be established.

smsmith
Moderator

User avatar
 
Posts: 18871
Joined: December 7th, 2004, 8:51 pm
Location: Illinois

Post Posted May 29th, 2014, 9:50 am

rsx11m wrote:Thus, let's see what's happening over the next two weeks, but a useful first step would certainly be to identify and nominate those candidate fixes for 2.26.1, by whatever mechanism can be established.

How do we identify and nominate things that should be included in 2.26.1? Is there a bug open for that? I've got a couple bugs that I think are already fixed or just need the Firefox counterpart landed. I want to make sure they get moved along.
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

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

Post Posted May 29th, 2014, 10:39 am

The most important ones are certainly the 30.0 security fixes which would be publicized in the security advisories. It is my understanding that Callek will skim those whether or not they can be fixed in the dot release (the problem for us "normal" people is that we don't have access to these bugs, thus can't tell how important they are and what effort is involved to make them work on a 2.26.1 release branch). Beyond that, if you have a specific bug/patch in mind that should be included, my suggestion would be to nominate it for approval-comm-release and/or to set a needinfo request for Callek to get his attention.

smsmith
Moderator

User avatar
 
Posts: 18871
Joined: December 7th, 2004, 8:51 pm
Location: Illinois

Post Posted May 29th, 2014, 10:59 am

Well here's the two bugs I am thinking of:
https://bugzilla.mozilla.org/show_bug.cgi?id=368266
https://bugzilla.mozilla.org/show_bug.cgi?id=1016759

The second one needs these two (probably!) to be pushed to the 2.26.1 release branch to fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=921942
https://bugzilla.mozilla.org/show_bug.cgi?id=952401

As someone in the know, if you could do whatever it takes to see if those can land in 2.26.1, I would be grateful. I don't think I have nominating "rights".
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

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

Post Posted May 29th, 2014, 11:37 am

smsmith wrote:Well here's the two bugs I am thinking of:
https://bugzilla.mozilla.org/show_bug.cgi?id=368266

This is MailNews Core and landed for Gecko 29.0, thus should be in SM 2.26 already.

The second one needs these two (probably!) to be pushed to the 2.26.1 release branch to fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=921942
https://bugzilla.mozilla.org/show_bug.cgi?id=952401

This won't work, the patches will need to be ported from browser/ to suite/ which may or may not be straight-forward, depending on the extent that the SeaMonkey's session restore feature follows the Firefox implementation.

smsmith
Moderator

User avatar
 
Posts: 18871
Joined: December 7th, 2004, 8:51 pm
Location: Illinois

Post Posted May 29th, 2014, 12:43 pm

rsx11m wrote:
smsmith wrote:Well here's the two bugs I am thinking of:
https://bugzilla.mozilla.org/show_bug.cgi?id=368266

This is MailNews Core and landed for Gecko 29.0, thus should be in SM 2.26 already.

Right, but it's not. There was some problem with the patch and the followup didn't make 2.26. See comment 12 of that bug and thereafter.

rsx11m wrote:
smsmith wrote:The second one needs these two (probably!) to be pushed to the 2.26.1 release branch to fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=921942
https://bugzilla.mozilla.org/show_bug.cgi?id=952401

This won't work, the patches will need to be ported from browser/ to suite/ which may or may not be straight-forward, depending on the extent that the SeaMonkey's session restore feature follows the Firefox implementation.

Sigh. It sucks that Firefox can break a SM feature but when they fix it in Firefox, it doesn't fix it in SM.
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

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

Post Posted May 29th, 2014, 12:59 pm

smsmith wrote:Right, but it's not. There was some problem with the patch and the followup didn't make 2.26. See comment 12 of that bug and thereafter.

I see, commented and follow-up patch nominated.

smsmith wrote:Sigh. It sucks that Firefox can break a SM feature but when they fix it in Firefox, it doesn't fix it in SM.

Happens all the time, unfortunately (also for Thunderbird).

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

Post Posted May 30th, 2014, 7:43 pm

Bug 1018509 - (SM2.26.1) Tracking bug for build and release of SeaMonkey 2.26.1.

ewong wrote:This is a tracking bug for Build and Release of SeaMonkey 2.26.1
We expect an actual release on Saturday, 14th June.

Philip Chee

User avatar
 
Posts: 6457
Joined: March 1st, 2005, 3:03 pm

Post Posted May 31st, 2014, 5:28 am

rsx11m wrote:
smsmith wrote:Well here's the two bugs I am thinking of:
https://bugzilla.mozilla.org/show_bug.cgi?id=368266

This is MailNews Core and landed for Gecko 29.0, thus should be in SM 2.26 already.
Contains a string change. Sorry but we can't land any string changes in Beta or Release.

Phil

[rephrase]We can't land any string changes in Beta or Release without majorly pissing off our translation volunteers who will then throw their hands up in the air and walk off in disgust. Then SeaMonkey 2.28 will only be in English.[/rephrase]

Phil

smsmith
Moderator

User avatar
 
Posts: 18871
Joined: December 7th, 2004, 8:51 pm
Location: Illinois

Post Posted May 31st, 2014, 7:25 am

Understood. I don't want to rock the boat for this. What are the chances it could get landed for 2.28?

What about the session restore bug?
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

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

Post Posted May 31st, 2014, 10:13 am

Philip Chee wrote:Contains a string change. Sorry but we can't land any string changes in Beta or Release.

Oops, thanks for pointing that out - I didn't check that before nominating... :oops:
I've cancelled the requests.

smsmith wrote:Understood. I don't want to rock the boat for this. What are the chances it could get landed for 2.28?

As it would have been in 2.27, it definitely will be in 2.28 (currently aurora).

What about the session restore bug?

Bug 1016759 doesn't even have a patch for trunk yet, thus not going to happen unless someone is really fast porting those patches and getting them reviewed.

-Px-

User avatar
 
Posts: 380
Joined: April 20th, 2011, 1:56 am

Post Posted June 1st, 2014, 1:55 am

rsx11m wrote:
What about the session restore bug?

Bug 1016759 doesn't even have a patch for trunk yet, thus not going to happen unless someone is really fast porting those patches and getting them reviewed.

The question is - how Firefox fix this issue, as patch caused that problem was copy/paste from corresponding FF patch. I will look on it later today, and if Firefox fix is complicated then create a patch with just revert that one line change

Return to SeaMonkey Builds


Who is online

Users browsing this forum: No registered users and 1 guest