On 11-07-30 9:26 AM, Bill Davidsen wrote:
get-funky.dig wrote:
I'm afraid... seeing this concerns me.
Please don't let Seamonkey become Firefox's “red-headed-stepchild”.
Please let us not suffer the nonsensical patterns of late from that
cr*p-factory (i.e. paraphrased, "following more the Update Schedule,
and borrowed nomenclature; updates scheme of Google Chrome") for the
In-Kids' Club.
The reason Chrome can run that way is that Google has resources to
provide fixes in parallel with features. Mozilla seems to have decided
to go to a "mostly new features" resource allocation (I say seems, based
on what's released). SM lacks the resources to do that, when new
features take 100% of the resources there's little effort put into bug
fixes. The project is allowed to exist but treated like a charity, from
what I see. Note that I am not "inside," I just read the endless posts
from SM people saying "we don't have the resources to do that."
Which is why users can't code stuff themselves and get it into the SM
releases, accepting a feature would mean maintaining it forever.
The changelog for the latest release can be found at
<http://www.seamonkey-project.org/releases/seamonkey2.2/changes>. There
are plenty of bug fixes.
--
Chris Ilias <http://ilias.ca>
Mailing list/Newsgroup moderator
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
