690041 - (SM2.4.1) Tracking bug for build and release of SeaMonkey 2.4.1 Oilspill Release

Status: RESOLVED FIXED

(SeaMonkey :: Release Engineering, defect, P1)

Description

[Justin Wood (:Callek)]

+++ This bug was initially created as a clone of Bug #688682 +++

2.4.1 is to be an oilspill release for the Gecko 7.0.1 chemspill

Comment 1

[Tony Mechelynck [:tonymec]]

(In reply to Justin Wood (:Callek) from comment #0)
> +++ This bug was initially created as a clone of Bug #688682 +++
> 
> 2.4.1 is to be an oilspill release for the Gecko 7.0.1 chemspill

after fixing bug 680802 and porting to all Firefox branches including release, is that it?

Comment 2

[Justin Wood (:Callek)]

Attachment: config for SM 2.3.3 -> 2.4.1 partial update

Comment 3

[rsx11m]

Thunderbird has included the fix for bug 690267 into their 7.0.1 oilspill.
Respin 2.4.1 for a second build to get it fixed for SeaMonkey as well?

Comment 4

[Ian Neal]

(In reply to rsx11m from comment #3)
> Thunderbird has included the fix for bug 690267 into their 7.0.1 oilspill.
> Respin 2.4.1 for a second build to get it fixed for SeaMonkey as well?

Yes, it would be good but depends at what stage Callek is in the process.

Comment 5

[rsx11m]

Ok, I see it on the FTP releases site already, thus may be too late by now...

Comment 6

[rsx11m]

Actually, it's on http://www.seamonkey-project.org/ already, thus definitely too late to pick up any more fixes (should have checked there first, oops!).

Comment 7

[Justin Wood (:Callek)]

(In reply to rsx11m from comment #6)
> Actually, it's on http://www.seamonkey-project.org/ already, thus definitely
> too late to pick up any more fixes (should have checked there first, oops!).

Yes, thunderbird was able to spin the release later than we were, and when I started the spin, the issue was even unknown to me.

I will pick it up if there is to be a SM 2.4.2, and I plan to create an addon to fix it as well.