Stanimir Stamenkov wrote:
Mon, 08 Aug 2011 14:27:03 -0400, /Rostyslaw Lewyckyj/:
MCBastos wrote:
First of all, I reject the premise that FF would be "churning half-baked
products". This is simply not true. In fact, it has been argued that the
new rapid-release schedule IMPROVES quality, since each release goes
through twelve weeks of testing (Aurora and Beta stages) with *no new
features added*, just debugging. In the old scheme, there was always the
temptation to add new features with the product close to release, since
the next release would be maybe a year away. And sometimes those new
features *were* half-baked.
So how many weeks of pure debugging and actual test suite testing did
SM 2.1 receive (in addition to testing by the FF and TB team testing?
[keeping in mind that SM has lots of code filched from FF & TB])
Also with 'an expected release maybe a year away' why were the new
features half-baked previously? A year is surely long enough to test.
And how about 2.2 ? And how about 2.3 ?
And how about repairing in 2.2 bugs discovered after release in 2.1?
And in 2.3 repairing bugs from 2.1 and/or 2.2?
(There have, I admit, promises to repair in 2.4 or later, some problems
introduced in 2.1 :-) )
"A year is surely long enough to test."
I don't think the SeaMonkey devs have ever had a full year for testing a
supposedly frozen product. Even with the previous Mozilla release cycle,
the longer time between releases meant more features developed to the
very end of the cycle, and then more stuff for the SeaMonkey developers
to catch up with. So no, I don't think and my experience is, SeaMonkey
has not been more stable having to release in longer intervals. The
shorter release cycle means less breaking changes would appear with
releases, the end users will be involved much more in identifying
problems with new changes, and these problems could be addressed much
faster, don't having to wait 1 or 2 years just to come up with the next
major release.
Okay if that's the case here is one for you . I tried the 2.3.b3 the
other day. Just to see if there was improvement.
Well PDF still doesn't work though all my plugins work except the one
for PDF. (Use a Mac).
However despite my transferring over copies of my Bookmarks from 2.0.14
profile to the (everything even the html files) not a single one showed
up. I have hundreds (while I don't go to everyone daily I do go to all
of them from time to time.
So I'm not move to 2.1, 2.2, 2.3, 2.4 until PDF from within the browser
is addressed and every one of my bookmarks even down to what's in
personal Bookmarks come over unscathed.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:[email protected]
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
