Bill Davidsen wrote:
I'm a fan of feature release followed by n (n>=1) bug fix releases, so you get a usable version fairly often, like stability releases for the Linux kernel, that kind of thing.
Me too, but as I explained in some other post, we don't have much of a choice anymore for the most part. As far as the address book breakage is concerned: We could have done a minor version update for that if we had found the issue earlier (the breakage on the development branch, trunk, was known and much larger, but the release branch d&d issue was unknown) *and* had a reviewed (!) fix in hand. The fix that I'm talking about has only been finished about a week ago, in time for SM 2.3, which is not too far off anymore (currently in beta), so releasing a 2.2.1 at this point doesn't make much sense.
The fact that 2.2, with broken address book, was not considered a brown bag release and quickly followed by 2.2.1 indicates that quantity is more important than quality.
2.2 was rushed, so much is true.
I know SM uses some shared TBird code, the one person I know who uses TBird tells me address book is still broken in the nightly she tried. Sigh.
I don't think that's true. The TB developers made a change that broke us (because we were missing a part on our side), not the other way around.
I'm grateful for the work people do, but I think the whole Mozilla effort has lost its way. It feels as if Firefox is the only thing which still gets QA resources and fixes in a timely manner.
90% true. The other 10% is for TB. [Note: IMO]
And IIRC the fixes in SM address book were rejected for TBird,
> so it would have to be maintained in SM long term. Again, I think you got something wrong there. Greetings, Jens -- Jens Hatlak <http://jens.hatlak.de/> SeaMonkey Trunk Tracker <http://smtt.blogspot.com/> _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
