NoOp schrieb:
There are thousands of 2.0.x SeaMonkey users (at least one would hope
so) out there that still have this issue. Marking the bug as 'FIXED' on
a yet to be released 2.1 trunk IMO simply doesn't cut it IMO.
"FIXED" always means "fixed in the version set as target milestone
and/or the current development version". You're right that there are
thousands of SeaMonkey 2.0.x users and exactly that's why we don't
magically change the behavior with a possibly silent security update
(unless we have to for security reasons) as then they'd start to
mistrust our security updates.
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community needs answers to. And most of the time,
I even appreciate irony and fun! :)
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
