Hi bfo
bfo wrote > > I would be happy if I achieve the change in base workflow - new feature in > the codebase? Splendid! But unit tests, testcases and manual testing done > before commiting. QA OKeyed the feature? Then you can commit. > As an ex-QA member, I think I should warn you that LO is not that type of managed project. It is a Developer driven project where QA contribution is welcome but it has no weight (or very little) on the succession of events. QA does not okay or stop anything. QA only warns devs if there are show-stoppers. At the pace of releases there is really not much more it can do. Apparently this (time based release) development model works for other OSS, but I believe that is because they must have a much larger QA community... Regards, Pedro -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Fwd-tdf-announce-The-Document-Foundation-announces-LibreOffice-3-6-with-a-wealth-of-ns-tp4000177p4001013.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
