Canasta wrote:
> I've been using and testing Mozilla since public builds became
> available. I've always been impressed by the work the project has done.
> I'm not a C++ programmer myself, so my contribution has been limited to
> testing the standards implementations and filing bugs.
>
> I've gotten the impression over the past few months or so that
> regression problems are becoming severe. Even "milestone" builds have
> very apparent and fundamental usability problems their predecessor
> milestones didn't.
>
> Would any of the developers agree with such an assessment? Is there
> anything we nondevelopers can do to help alleviate this situation?
> What's Mozilla's greatest need from us at this time as we approach 1.0?
>
>
I'm not a developer, but I've been keeping track of as much
as I can understand on an almost daily basis to say that I
think this is expected because there have been several major
checkins in the past several months. This is an
unfortunately side effect that would get flattened out with
time, but some of the major checkins have included the new
cache, the new image library, XPCDOM, LDAP, BiDi, Outliner,
PSM2, and I'm probably missing more.
It's all for the better (XPCDOM shaved 2 MB off initial
memory use), but big landings have always meant increase
chance of regressions for a bit.
--
Alex <:3)~~
http://www.gerbilbox.com/newzilla/
