Closed Bug 684651 Opened 9 years ago Closed 8 years ago

Create/Update 2.4 Release Notes

Categories

(SeaMonkey :: Website, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: InvisibleSmiley)

References

()

Details

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

SeaMonkey 2.4 Beta 1 builds will be shipped today and the milestone needs relnotes when it appears.
initial version

RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.4/changes.en.html,v
done
Checking in src/releases/seamonkey2.4/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/changes.en.html,v  <--  changes.en.html
initial revision: 1.1
done
RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v
done
Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
initial revision: 1.1
done
RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.4/relnote.var,v
done
Checking in src/releases/seamonkey2.4/relnote.var;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/relnote.var,v  <--  relnote.var
initial revision: 1.1
done
Assignee: nobody → jh
Status: NEW → ASSIGNED
Blocks: SM2.4b2
For the b2 update, see bug 686174.
Blocks: SM2.4b3
Blocks: SM2.4
"Relevant security fixes are listed on Security Advisories for Firefox (Firefox 7)."

Shouldn't this point to the SeaMonkey-specific page for 2.2+ now that it exists?
http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html
(In reply to rsx11m from comment #3)
> Shouldn't this point to the SeaMonkey-specific page for 2.2+ now that it
> exists?
> http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html

Sure, why not. Excluding 2.2 though, since it matches FF 5 and the FF sec page has entries for it but the SM page doesn't.


Use SM-specific security pages now that they exist

Checking in src/releases/seamonkey2.3/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.3/index.en.html,v  <--  index.en.html
new revision: 1.17; previous revision: 1.16
done
Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
new revision: 1.2; previous revision: 1.1
done
Checking in src/releases/seamonkey2.5/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.5/index.en.html,v  <--  index.en.html
new revision: 1.3; previous revision: 1.2
done
Callek informed me about bug 680802, which we indeed suffer from, too (with any SM version >= 2.4, like FF >= 7). I went through reproducing the problem and all workarounds, then added a Known Issue. The issue details can be found in bug 680802 comment 15.

Added note about bug 680802 (add-on loss) and removed FB 1.7 issue

Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
new revision: 1.3; previous revision: 1.2
done
Checking in src/releases/seamonkey2.5/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.5/index.en.html,v  <--  index.en.html
new revision: 1.4; previous revision: 1.3
done
Added bookmarklets bug 688841 to Known Issues and removed en-GB/es-AR Help issue

Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
new revision: 1.4; previous revision: 1.3
done
Blocks: SM2.4.1
adapted bug 680802 Known Issue for 2.4.1

Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
new revision: 1.5; previous revision: 1.4
done
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
added note about download dir being remembered per site now (bug 536503)

Checking in src/releases/seamonkey2.4/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.4/index.en.html,v  <--  index.en.html
new revision: 1.6; previous revision: 1.5
done
Product: Websites → SeaMonkey
You need to log in before you can comment on or make changes to this bug.