From Fedora Project Wiki
(Scope of successful booting) |
m (Typo) |
||
| Line 11: | Line 11: | ||
* What is unique about Alpha blocker bugs and how can we capture that above (or tighten down in Beta and Final release sections)? | * 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 | * Make sure all ''MUST'' and ''SHOULD'' items from [QA/ReleaseCriteria] are integrated into the test plans referenced in the requirements | ||
* [[User:Bruno 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. | * [[User:Bruno|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. | ||
Revision as of 00:54, 21 November 2009
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.