A Williams wrote:
I think most - but not all - Seamonkey users have no problems with the
features coming a bit later, as long as the security holes are fixed.
Let the Firefox/Thunderbird users beta-test new features for us.
The problem is that it is difficult to have one without the other. The
security patches are for a code base which includes the new features -
hell - a large proportion of the security patches*are* for the new
features. Deliberately remaining a bit behind is a slippery slope.
It is unfortunate that the child (Firefox, Thunderbird) does not help
the parent a bit more with resources.
That's my perspective.
The hard part is that since Seamonkey is derived from FF and TB code
(and underneath, Gecko), then it's subject to the Gecko release cycle,
even for updates.
For Seamonkey, that can be mostly offset by working from Firefox ESR
releases, but even Firefox ESR and Thunderbird (which is functionally
ESR) are still working on the current every six weeks cycle.
The catch to working on the ESR builds is going to be that even ESR gets
periodic major upgrades, e.g., 31.xesr to 38.xesr. It's instructive that
while Thunderbird releases based on esr, there are still beta builds,
where new features (as I believe are imposed by updates to Gecko) are
being implemented, even if they're not a public release. Thus, if
you're not on Thunderbird's beta channel, you won't see it, but there is
a Thunderbird 39.0 beta in existence.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
