On 29/03/15 03:34, NFN Smith wrote:
WaltS48 wrote:
>Would it be better not to touch that part of the code then ? Would it
>be better to perform regression testing ?
>Or a broken feature is not high priority ? Who knows ?
The Gecko code gets changed by paid Mozilla developers and volunteers
for use in Firefox. If that breaks something in SeaMonkey or
Thunderbird...
Yep. Sometimes, new problems aren't introduced by Seamonkey or
Thunderbird developers, but inherited from updates made, as a part of
the Rapid Release cycle for Gecko.
There are times when I wonder if Mozilla is so focused on Firefox, that
the Gecko and Firefox developers don't give adequate consideration to
the effects of changes on derivative and dependent works -- not just
Seamonkey and Thunderbird, but things like Lightning and extensions, and
projects such as PaleMoon, FossaMail, Waterfox, Galeon, Flock, K-meleon,
etc.
One would guess that "the Gecko and Firefox developers don't" want
people using all the other stuff. "We" should all be using FF, ITHO (in
their humble opinion) of course! ;-)
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101
SeaMonkey/2.32 Build identifier: 20141218225909
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101
SeaMonkey/2.33 Build identifier: 20150215202114
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
