Rostyslaw Lewyckyj schrieb:
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?
Too little automated testing, we need more tests to be written and are
happy about people doing those, feel free to contribute.
And how about 2.2 ? And how about 2.3 ?
Those have more testing because the stable phase is much longer with the
new process, believe it or not. Previously, new features could land up
to the last beta in practice, and they did get testing only through the
one or two RCs, with 2-3 weeks, maybe a month in total of being out
there for testing before release. With the new process, no features can
land in aurora or beta phases, only fixes and turning off of
non-finished features are allowed, which makes us have ever
feature-stable version being ready and in testing for 12 weeks before
release. That's more than we ever had before, so the result should be
more stable and better tested.
Sounds fun to say that a faster release cycle results in more testing
and more stability, but a number of very intelligent people at Mozilla
thought long and hard about this to make exactly that happen.
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community should think about. And most of the
time, I even appreciate irony and fun! :)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
