I believe the schedule (http://fedoraproject.org/wiki/Releases/11/Schedule) has this information. The full task-view is available at http://poelstra.fedorapeople.org/schedules/f-11/f-11-all-tasks.html

Nope I think of this "check list" to be what we need to do during alpha beta ( stages ) and at
the beginning of each release cycle. We should create a "check list" under QA on the wiki
with tasks that need to be checked on regularly for example urls on the QA namespace that need to point to correct release location test_days updated for release.

We would create a Check list page on the wiki somewhat like this..

https://fedoraproject.org/wiki/User:Johannbg/Draft/QA/Task_schedual

I'm open to this idea, but don't want to create a tracking mechanism for which we have no process yet. Also, I believe we have a mechanism for recording/scheduling QA tasks during a release in the QA Schedule (http://poelstra.fedorapeople.org/schedules/f-11/f-11-quality-tasks.html). Perhaps it's worth:
* revisiting whether the schedule of current tasks is at appropriate times,
* and if the actions required to full fill the tasks is documented?

Looking at the tasks you've proposed, not sure if they are just rough examples or proposed tasks (https://fedoraproject.org/wiki/User:Johannbg/Draft/QA/Task_schedual):
* Check if Test Cases have been feature updated - The schedule current has a review "comb" of the feature pages for QA input
* Check that all urls on wiki point to correct location - can you clarify, I'm not sure what you mean by this?
* Check if rss feeds point to current rawhide - is this related to your fedora-infrastructure proposal, or something that exists currently?

Thanks!
James

Replying to [comment:3 jlaska]:

I'm open to this idea, but don't want to create a tracking mechanism for which we have no process yet. Also, I believe we have a mechanism for recording/scheduling QA tasks during a release in the QA Schedule (http://poelstra.fedorapeople.org/schedules/f-11/f-11-quality-tasks.html). Perhaps it's worth:
* revisiting whether the schedule of current tasks is at appropriate times,
* and if the actions required to full fill the tasks is documented?

This is idea is not meant to be as a replacement nor is related to http://poelstra.fedorapeople.org/schedules/f-11/f-11-quality-tasks.html

Looking at the tasks you've proposed, not sure if they are just rough examples or proposed tasks (https://fedoraproject.org/wiki/User:Johannbg/Draft/QA/Task_schedual):

They are just rough examples

• Check if Test Cases have been feature updated - The schedule current has a review "comb" of the feature pages for QA input

Dont think that existed at this ticket creation but an example that would make it to this check list would be make sure that all features have been QA approved before beta

• Check that all urls on wiki point to correct location - can you clarify, I'm not sure what you mean by this?

As a new release is released and ofcourse another one is then obsoleted go through all the QA pages and make sure all links point to their correct url Task/check Item..

• Check if rss feeds point to current rawhide - is this related to your fedora-infrastructure proposal, or something that exists currently?

Something that exist currently when going through some old QA pages I noticed that we were still pointing to F10 instead of F11 ( rawhide ) bugzilla url if I can recall correctly.

This essentally is just an checklist for task/actions that need to be performed during every release cycle/milestone

JBG

Thanks for the reply.

Replying to [comment:4 johannbg]:

This essentally is just an checklist for task/actions that need to be performed during every release cycle/milestone

Yeah I agree that's useful. That's the intended use for the tasks listed in the QA schedule.

Check if rss feeds point to current rawhide - is this related to your fedora-infrastructure proposal, or something that exists currently?
Something that exist currently when going through some old QA pages I noticed that we were still pointing to F10 instead of F11 ( rawhide ) bugzilla url if I can recall correctly.

Would having a release specific QA portal page fill the need here? This page would outline
* planned test efforts (Test Days, Triage events, etc...)
* provide release specific QA links?
* What else?

I think James is right here in that the QA schedule is meant to cover this. I would like to be able to link out from the schedule to the appropriate SOP for each event listed on it. I went through the F16 schedule right at the time F16 started and verified that we actually do have an appropriate SOP to link to for just about every event listed on the schedule - so I think we're actually pretty well covered here, these days. The only remaining task is to have the links actually added to the schedule, which I need to keep bugging Robyn about.

Replying to [comment:6 adamwill]:

The only remaining task is to have the links actually added to the schedule, which I need to keep bugging Robyn about.

This sounds a lot like some of the stuff roshi and I have been discussing. But what "schedule" are you referring to here, and are links still an issue for that?

http://fedorapeople.org/groups/schedule/f-20/f-20-quality-tasks.html

and yes, still an issue. what I would like is if the calendar had links out to SOPs for all the tasks. I don't know if we're planning to move to fedocal now, or something.

I don't think having this ticket open is serving much of a purpose any more. I think there are a few things in this area to work on, though:

• Getting SOP links from the schedule pages
• Adding a few more tasks to the schedule
• Clarifying who's responsible for blocker tracker bug creation (I do it at present, but FPM does all the other 'Bugzappers' housekeeping stuff), and adding it to QA schedule if necessary

Filed https://fedorahosted.org/fedora-qa/ticket/455 for one of those, mailed jskladan about the others.