Thanks for your reply, Caio :) On 13/12/2006, at 11:03 AM, Caio Tiago Oliveira wrote:
Clytie Siddall, 12-12-2006 01:40:Today is release day. I haven't seen anything about any formalities for QA before release, but thought I had better check. Do I need to do anything specific to state that OpenOffice.org 2.1 should be release with support for our language? I've found only very minor bugs, and hardly any of those related to our language. We will continue to test after release.Does it have passed all the smoke tests, all of the automatized tests, etc.?
Exactly which tests are these?I'm confused as to whether TCM and testtool are alternatives, or parts of the whole procedure.
Specifically, which tests does a build have to pass, to be released?We really need this documented on the website or in the wiki, then send the link to affected lists (at least the l10n list).
See this issue as an example: <http://www.openoffice.org/issues/show_bug.cgi?id=72496>
Thanks. An example is always useful.
What can I tell you is that it's up to your team to decide if it should be released, i.e., the bugs you found are very minor and should be better to released anyway.
The builds have worked fine in production, and my TCM of the Mac Intel build has also only found tiny bugs so far, not related to our translation. But I'm not happy releasing on that if it's not the procedure.
Yet I don't know how I'm going to get the tests done for Linux and Windows.
You can just tell in this list (I've seen some doing it), but it's better to file an issue in the QA component of IssueTracker.
OK.
We should formalize and organize it better, by the way.
+10from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
