856963 - (SM218-RELNOTE) Create/Update 2.18 Release Notes

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Edmund Wong (:ewong)]

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

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

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

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

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


SeaMonkey 2.18 Beta 1 builds will be built soon.

These relnotes can be (begun to be) prepared ahead of the release date, but need to be out by our first beta release.

Comment 1

[rsx11m]

Major new feature for the "What's New" highlights:

"SeaMonkey 2.18 now offers a safe browsing feature to block potentially malicious websites reported as attack sites (malware) or web forgeries (phishing)." - bug 477718

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

Again I wasn't able to fill in the changes page in time. However I incorporated comment 1 (thanks rsx11m!).

initial version

RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.18/changes.en.html,v
done
Checking in src/releases/seamonkey2.18/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/changes.en.html,v  <--  changes.en.html
initial revision: 1.1
done
RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.18/index.en.html,v
done
Checking in src/releases/seamonkey2.18/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/index.en.html,v  <--  index.en.html
initial revision: 1.1
done
RCS file: /www/seamonkeyproject-org/src/releases/seamonkey2.18/relnote.var,v
done
Checking in src/releases/seamonkey2.18/relnote.var;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/relnote.var,v  <--  relnote.var
initial revision: 1.1
done

Comment 3

[Jens Hatlak (:InvisibleSmiley)]

filled in b1 changes and prepared b2 ones

Checking in src/releases/seamonkey2.18/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/changes.en.html,v  <--  changes.en.html
new revision: 1.2; previous revision: 1.1
done
Checking in src/releases/seamonkey2.18/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/index.en.html,v  <--  index.en.html
new revision: 1.2; previous revision: 1.1
done

Comment 4

[rsx11m]

https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2013-04-30#Extensions_Compatibility_Tracking

> Might need to point out in release notes that users needs to install the
> Lightning beta versions for the SeaMonkey releases (as Lightning follows
> Thunderbird 17.0.x release schedule)

The current information in the release notes is somewhat hidden, "Lightning provides versions compatible with the latest SeaMonkey beta through its Development Channel which has an own section at the bottom of the Lightning add-on page <link>." Some posts in the MZ forums suggest that users may not find it easily. Any place to more specifically refer to Lightning (and possibly Enigmail) versions, or highlight them as subsections of the Extensions section?

I've tried a more direct link referring to the to the Development section at https://addons.mozilla.org/en-US/seamonkey/addon/lightning/#install-beta but it won't open the tab as it's hidden by default. Thus, maybe link to 2.3b1 using https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/?page=1#version-2.3b1 in addition to the generic link to the add-on page?

Comment 5

[rsx11m]

Setting plugin.expose_full_path to get the full plugin paths in about:plugins has no longer any effect (bug 870590, fixed in 2.21 by rewrite with bug 661961).

Comment 6

[rsx11m]

(make that 2.19 = Gecko 22.0, getting confused with version numbers...)

Comment 7

[Jens Hatlak (:InvisibleSmiley)]

Thanks for the heads up rsx11m, I had accidentally experienced this bug, too, but had not taken the time to dig deeper yet.

noted regression bug 661961 and prepared beta 5

Checking in src/releases/seamonkey2.18/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/changes.en.html,v  <--  changes.en.html
new revision: 1.7; previous revision: 1.6
done
Checking in src/releases/seamonkey2.18/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/index.en.html,v  <--  index.en.html
new revision: 1.4; previous revision: 1.3
done

Comment 8

[rsx11m]

Any idea on how to better guide the users in finding the correct Lightning version? (comment #4)

Comment 9

[Frank Wein [:mcsmurf]]

Minor suggestion for now: In this sentence "Lightning provides versions [...]" format the "Lightning" as bold. Then it's at least easier to spot in that paragraph. We could also link to https://addons.mozilla.org/en-US/seamonkey/addon/lightning/#beta-channel, but unfortunately the page position does not stick to the button of the page as it loads the user comments after the page has finished loading (AJAX).

Comment 10

[Frank Wein [:mcsmurf]]

*bottom

Comment 11

[rsx11m]

It would be possible to link to the versions page instead with a version target:
https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/?page=1#version-2.3b1 in this case for 2.18.

As was pointed out in today's meeting, that version may not exist (yet), or there is a b2 on the Lightning side, etc. Also, changing the version number manually isn't feasible. However, it could be calculated from [% rnote.version %] by subtracting 15 from the minor version number (SM 2.18 - .15 = Lightning 2.3).

Just mentioning in the text which version is needed in that section should help resolving any ambiguity, but would need some coding to do it automatically.

Comment 12

[Jens Hatlak (:InvisibleSmiley)]

added a note and page for skipped 2.18 final 

RCS file: /www/seamonkeyproject-org/src/releases/2.18.en.html,v
done
Checking in src/releases/2.18.en.html;
/www/seamonkeyproject-org/src/releases/2.18.en.html,v  <--  2.18.en.html
initial revision: 1.1
done
Checking in src/releases/seamonkey2.18/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/changes.en.html,v  <--  changes.en.html
new revision: 1.8; previous revision: 1.7
done
Checking in src/releases/seamonkey2.18/index.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.18/index.en.html,v  <--  index.en.html
new revision: 1.6; previous revision: 1.5
done

Comment 13

[Jens Hatlak (:InvisibleSmiley)]

(In reply to Frank Wein [:mcsmurf] from comment #9)
> Minor suggestion for now: In this sentence "Lightning provides versions
> [...]" format the "Lightning" as bold. Then it's at least easier to spot in
> that paragraph.

That's what I'll do for the 2.19 relnotes; the 2.18 ones are done.