Hi Raphael, all > I believe the 4.1.4 shows us, that we have to do a better job in QA. A > minor release should never go to a rc5. I believe we all (and I pointing > my finger to myself) underestimated the regression risk at the 4.1.4.
+1 > So, to do a better job in the 4.2.0 I propose the following changes. > > - Define test areas, where tester should keep an extra eye on it. (based > on the changes) > - Doing Developer Snapshots again in a 2 Week frequency (or so) > - Switch the AOO Profile for the snapshots to AOO-Dev > - mobilize the willing testers to keep a critical eye on this builds > - maybe also run the automated tests for Apache OpenOffice. As a user/tester/part-timeQA I agree to all points. But, please include Language packs in Developer Snapshots. Running a build with an un-matching language pack causes very serious usability problems (this is IMO the only advantage of including all languages in a single installer). Creating a blank AOO-Dev profile is a two edged sword: you get a clean start (and avoid trashing the user's work profile) but it isn't a realistic usage (and therefore testing will not find those day to day problems that resulted in the need to go to RC5) Maybe a middle term would be to create a separate Dev profile that is a copy of the user's profile (including all extensions)? > The idea is to make the bug cycle shorter. Improvements should be tested > right after the implementation and not short before the release. A fresh > bug is easier to fix as a old one. That is the ideal situation. But requires more communication (the QA mailing list is unused for months) and especially more man power (on all platforms!). The only way to get more users is to add needed/missing features and get visibility... Regards, Pedro --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
