Ticket #259 (closed task: wontfix)

Opened 2 years ago

Last modified 23 months ago

Review Fedora 17 feature list and co-ordinate with owners of significant features to create test plans

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

Description

We should have someone responsible for reviewing the Fedora 17 feature list and ensuring a good test plan is in place for any significant and potentially disruptive feature. This ticket is for the general process of reviewing the entire feature list; whoever does this may well choose to create separate tickets for the test plans for specific features.

If you're interested in working on this, please feel free to assign the ticket to yourself.

Change History

comment:1 Changed 2 years ago by adamwill

  • Cc hongqing added
  • Owner set to twu

comment:2 Changed 2 years ago by adamwill

Tao, I know this is a big ticket, so please feel free to ask for any help if you need it. I've CCed Hongqing, with the intention that you can work on this ticket together.

The workflow I'd expect here is for you to look through the full accepted feature list, identify any features that look like they might be particularly needing of QA, and contact the feature owners. The goal is to make sure we get the features landed in plenty of time and ideally we test them out as early as possible, so there aren't big surprises when we hit Alpha and Beta validation.

Just as a quick start, the kinds of features I'd expect to be a really high priority are:

I don't think all proposed features have yet been reviewed, so keep an eye on FESCo meetings for more approved features.

Obviously the anaconda UI rewrite is another big one, though it doesn't actually seem to have been formally accepted as a feature yet.

comment:3 Changed 2 years ago by jdulaney

Just as an aside, I do not see btrfs becoming a feature as there is still no fsck. Most of the major features of btrfs do have test cases at this point.

comment:4 Changed 23 months ago by adamwill

  • Resolution set to wontfix
  • Status changed from new to closed

Well, 17 is done. We didn't do any significant work on this ticket, so closing as wontfix.

Note: See TracTickets for help on using tickets.