Ticket #257 (closed task: fixed)

Opened 2 years ago

Last modified 2 years ago

Create and maintain F17 install test plan

Reported by: adamwill Owned by: hongqing
Priority: critical Milestone: Fedora 17
Component: Wiki Version:
Keywords: Cc: twu, hongqing
Blocked By: Blocking:

Description

We need an installation test plan for Fedora 17, can be modelled on previous ones:

etc. Note that some of the copypasta on that page dates back to well before the current matrices and blocker process were in operation and could probably be revised.

The main benefit of the test plan should be to plan for major changes to the installation process caused by F17 features. The anaconda UI rewrite is an obvious one, but there may be others. For F16, for instance, we could have used this document to better handle the grub2 and GPT changes. So for F17 we should take advantage of the opportunity.

This needs to be in place ahead of F17 Alpha TC1.

Change History

comment:1 Changed 2 years ago by adamwill

  • Component changed from Proventester Mentor Request to Wiki
  • Priority changed from major to critical

comment:2 Changed 2 years ago by adamwill

  • Owner changed from adamwill to hongqing

comment:3 Changed 2 years ago by adamwill

This ticket is a bit open-ended, I realize; it may turn out not to be a really important thing to do. But it's worth taking a look at. Obviously you'll want to talk directly to the anaconda team on this one, and look back through previous install test plan pages to see what was done there. It's also worth taking out some of the stuff that's been made obsolete by the current blocker review and release validation processes.

If you're having trouble figuring out what to do here, just yell!

comment:4 Changed 2 years ago by hongqing

  • Resolution set to fixed
  • Status changed from new to closed
  • Cc twu, hongqing added; twu hongqing removed

the Fedora install test plan can be found at https://fedoraproject.org/wiki/QA:Fedora_17_Install_Test_Plan
please feel free to update it if necessary.

Note: See TracTickets for help on using tickets.