Greetings,
What is the SOP to push AutoQA code for review? Just attach them as attachments or
are there any other requirements? This is my first time doing this.a Thanks.
Hongqing
I have just pushed commit fa55089 [1]. It means that autoqa library is now automatically transferred to autotest clients before every test run. In the development environment you probably used NFS mounts on the clients [2]. You should delete the mounts after you pull the new code. They are no longer necessary (and it could overwrite you something in the process).
[1] https://fedorahosted.org/autoqa/ticket/254
[2] https://fedoraproject.org/wiki/AutoQA_Development
Now that 0.6.0 has been released and we haven't seen any new issues,
it's time to start looking at 0.7.0. Since we're all working on getting
Fedora 16 Alpha out the door, I think that we're going to hold off on
some of the major work for the time being but that doesn't mean we
can't start planning.
I'd like to schedule a teleconference for Thursday but before I do,
let's get a list together of the proposed features. Once we have a
list, I'll schedule a meeting.
My proposals are holdovers from 0.6.0 that didn't get finished:
* #347 - Test results are sometimes linked incorrectly in bodhi
- https://fedorahosted.org/autoqa/ticket/347
* #355 - Determine Use Cases for Functional Self Tests
- https://fedorahosted.org/autoqa/ticket/355
* #353 - Create AutoQA Functional Self Test Cases
- https://fedorahosted.org/autoqa/ticket/353
Any other proposals?
Tim