Additional Notes, Thoughts, and Questions
- It would be valuable to work in some bullets that address meeting the needs of the target audience for this release
- What are the needs of the target audience for the Alpha release?
- What are the distinguishing features of the Alpha Release?
- How is it different from Beta and Final? It would be helpful to call this out at a high level even if the distinguishing differences are in the required test cases.
- What problem is the Alpha trying to solve?
- How will decide if the Alpha Release is a success?
- How good does the Alpha need to be?
- Do we put the Fedora distribution or project at risk if we don't meet this criterion?
- Do we negatively affect users or others if we don't meet this criterion?
- What is unique about Alpha blocker bugs and how can we capture that above (or tighten down in Beta and Final release sections)?
- Make sure all MUST and SHOULD items from [QA/ReleaseCriteria] are integrated into the test plans referenced in the requirements
- Bruno: For "The installed system boots and starts up properly" does that mean on a single machine? It seems to be often the case that their are hardware specific bugs that prevent booting on some particular hardware.
- jlaska 16:12, 25 November 2009 (UTC) - Let's move this discussion to the list. There is some discussion there already on how best to capture common hardware and configuration issues, but we still need to track this down.
- Kparal : "# Execute all Fedora 13 test cases " - Fedora 13 Alpha test cases? Because in Beta and Final release criteria there is word "Beta" and "Final". Do we even have test cases different in different stages?
- jlaska 16:12, 25 November 2009 (UTC) - Thanks, I've adjusted the wording per your recommendation. As for the list of test cases, we don't have the list yet organized in the per-milestone view yet. I've been talking with liam for ideas on modifying QA:Fedora_12_Install_Test_Plan to adapt to this model. Ideas and suggestions are encouraged.