This relates to my question about formalities before release...
On 11/12/2006, at 2:09 AM, James Mckenzie wrote:
I don't know whether QA not being finished is a stopper or not. I haven't dealt with such a formalized QA process before.AFAIK, QA not being finished is a stopper.Definitely. QA needs to be done on a particular build for a particular language before usingin a production environment..
I was a bit panicked about, this, because I didn't have enough time to get through all the TCM tasks before the release date.
But when I compare the number of tasks I've done with those completed by other languages, they haven't finished them all either. So perhaps completing all of TCM isn't required for release.
I don't understand how we authorize release. On the information we (the vi project) have, including reports on previous 2.1 builds, our translation is certainly ready for release. We may get some very minor and esoteric bugs reported after release, but that's all.
Do I have to do anything separate to authorize release? This is my first release, so it's all new to me.
I see the QA process as continual, and I'm trying to fit the release procedures into that.
Thanks for any light you can shed on my confusion. ;)from 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
