883469 - (SM219-RELNOTE) Create/Update 2.19 Release Notes

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Edmund Wong (:ewong)]

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

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


SeaMonkey 2.19 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

[Jens Hatlak (:InvisibleSmiley)]

initial version

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

Comment 2

[rsx11m]

I don't know if bug 818340 on third-party cookies from visited websites should be added for 2.19 already, given that it's not the default yet per bug 851606, or if we want to wait until it's actually switched (assuming that this will eventually happen).

Anyway, proposed text (if the answer is "yes"):

"The acceptance policy for cookies from third-party websites can now be restricted to sites that you have explicitly visited before (bug 818340, bug 845353)."

Known issues (unless Neil's fix can still land for 2.19 final):

"In private browsing mode, opening a new private window will clear any private cookies which were accepted before (bug 874042)."

Comment 3

[rsx11m]

Looking at bug 885136 and bug 851606 comment #19, it appears that the default may not be switched to "visited 3rd-party cookies" until a global list is available to avoid certain false-positive/false-negative cases. Thus, mentioning that the new feature is available now and then again when it's made the default should be fine.

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

filled in TODOs

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

Comment 5

[Jens Hatlak (:InvisibleSmiley)]

Note to self: bug 841642 comment 5

Comment 6

[rsx11m]

(In reply to rsx11m from comment #2)
> Known issues (unless Neil's fix can still land for 2.19 final):
> "In private browsing mode, opening a new private window will clear any
> private cookies which were accepted before (bug 874042)."

This has landed on comm-beta, thus should be in 2.19 final after the merge.

Comment 7

[Jens Hatlak (:InvisibleSmiley)]

Platform changes: removed WebRTC (not available yet in SM)
Known Issues: added bug 888478 and fix version for bug 727414

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

Comment 8

[Andrea Govoni]

In the "Fixes in 2.19 Final" section of the changes page I see:
"Selecting saved search folders in MailNews could lead to a crash (bug 856768)."

Is bug 856768 ("Alter socorro regex args check") really the relevant bug number?

Comment 9

[Jens Hatlak (:InvisibleSmiley)]

(In reply to Andrea Govoni from comment #8)
> In the "Fixes in 2.19 Final" section of the changes page I see:
> "Selecting saved search folders in MailNews could lead to a crash (bug
> 856768)."
> 
> Is bug 856768 ("Alter socorro regex args check") really the relevant bug
> number?

No it's not. I was foolish enough to trust the information from comm-release changeset 586520179d8b (Neil seems to dislike copy&paste even when it's advised). The actual one is bug 857678. Will correct the entry later today.

Comment 10

[rsx11m]

Release notes still state "SeaMonkey 2.19 up to/including SeaMonkey 2.19 Beta 2" with other mentioning of 2.19b2 throughout the page while the other pages have been correctly updated. Was this missed or is it just a lag in the site propagating?

Comment 11

[Jens Hatlak (:InvisibleSmiley)]

(In reply to rsx11m from comment #10)
> Release notes still state "SeaMonkey 2.19 up to/including SeaMonkey 2.19
> Beta 2" with other mentioning of 2.19b2 throughout the page while the other
> pages have been correctly updated. Was this missed or is it just a lag in
> the site propagating?

This I actually missed, thanks for noticing!


corrected number of crash bug fixed in 2.19 Final, relnote version and 2.10 mirrorred flag

Checking in src/releases/2.10.en.html;
/www/seamonkeyproject-org/src/releases/2.10.en.html,v  <--  2.10.en.html
new revision: 1.5; previous revision: 1.4
done
Checking in src/releases/seamonkey2.19/changes.en.html;
/www/seamonkeyproject-org/src/releases/seamonkey2.19/changes.en.html,v  <--  changes.en.html
new revision: 1.5; previous revision: 1.4
done
Checking in src/releases/seamonkey2.19/relnote.var;
/www/seamonkeyproject-org/src/releases/seamonkey2.19/relnote.var,v  <--  relnote.var
new revision: 1.3; previous revision: 1.2
done