Hello, Thorsten Ziehm schrieb: > Hi Mathias, > > Mathias Bauer schrieb: > >> More testing on the master(!) would be very welcome. But on the CWS? >> This will make the "time to master" even longer and then again we are in >> the vicious cycle I explained in my first posting in this thread. > > Yes more testing on Master is welcome, that is true. But most testing > must be done on CWS. When broken code is in the master code line it > take too much time to fix it. And then you cannot do Quality Assurance. > You can make testing, but that has nothing to do with hold a Quality > standard! > > The time to master isn't a problem currently, I think. A general bugfix > CWS can be 'approved by QA' in 2 days. But when the master is broken, > you do not know, is the bug in the CWS or in the master. It takes longer > for checking the problems and this is what we have now. Reduce the time > to master will come, when the general quality of the master and the CWSs > is better. > > So more testing on CWS is also welcome!
Yes Full ACK to last sentence. And this is not only a task for the Sun people. The persons who are interested at a CWS must be able to test a CWS. And this also if they aren't able to build OOo on their own. This is nearly impossible to do it for people outside from Sun. The same concerns to external CWSes. If we should discuss it more detailed we can do it in a separated thread. Kind regards Mechtilde -- Dipl. Ing. Mechtilde Stehmann ## http://de.openoffice.org ## Ansprechpartnerin für die deutschsprachige QA ## Freie Office-Suite für Linux, Mac, Windows, Solaris ## Meine Seite http://www.mechtilde.de ## PGP encryption welcome! Key-ID: 0x53B3892B --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
