Hi all,
I've added two subprojects to the Task Manager. One for updating OpenCLX for
K3, and the other for testing.
So far, I have 3 tasks in the update subproject. I haven't assigned them
out to anyone yet. I'd appreciate it if you'd go over the tasks and email
back on which ones each of you would be able to do. Two of them are fairly
simple, one is a little more involved. This will give me a little bit better
of an idea of what sort of tasks each of us can take.
I haven't placed any items in the Testing subproject yet. I'm still a little
bit undecided on how to proceed there. Testing, potentially, could get VERY
involved. My thinking right now is that instead of complicated automated test
scripts, regression analysis, and really involved QA that it would be a
better use of resources to pick a selection of open-source Kylix applications
and use them to test out the components. I am of the opinion that we
shouldn't burden ourselves with test scripts until we actually start receiving
CLX bug reports and start fixing bugs. At this point, we can make a script
that identifies the bug in bad versions and tests for it in our 'fix' versions.
I'm interested in your feedback on all of this. Especially if you have other
ideas on testing, or you have ideas for tasks I missed.
Kurt.
--
_/_/_/ _/ _/ _/_/_/ _/_/_/ _/ _/_/_/ _/_/_/ _/_/ kfitzner@
_/ _/_/ _/ _/ _/ _/ _/ _/ _/ excelcia.org
_/_/ _/ _/ _/_/ _/ _/ _/ _/_/_/
_/ _/_/ _/ _/ _/ _/ _/ _/ _/ E-Dad
_/_/_/ _/ _/ _/_/_/ _/_/_/ _/_/_/ _/_/_/ _/_/_/ _/ _/ PGPid 0xF621EDAD
|
