Ticket #80 (closed enhancement: fixed)

Opened 7 years ago

Last modified 5 years ago

Add dual-boot release criteria

Reported by: jlaska Owned by: adamwill
Priority: major Milestone: Fedora 17
Component: Wiki Version:
Keywords: retrospective Cc: robatino
Blocked By: Blocking:



See RHBZ#590661 - GRUB bootloader should have a few seconds delay on a multi-boot setup


Due to RHBZ #590661, the dual-boot experience was not well understood and tested for the final release. It was discovered late and unclear whether this behavior was critical to Fedora success.

enhancement recommendation

The user experience of dual-boot scenarios was not well understood, as a result RHBZ #590661 did not clearly impact the release criteria. Recommend reviewing and making adjustments to the release criteria for dual-boot expectations.

Change History

comment:1 Changed 7 years ago by robatino

  • Cc robatino added

comment:2 Changed 5 years ago by adamwill

  • Owner set to adamwill
  • Status changed from new to assigned
  • Milestone changed from Fedora 14 to Fedora 17

This is still somewhat valid. We have added a release criterion to Final:

"The installer must be able to install into free space alongside an existing clean single-partition Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working"

It doesn't explicitly call out the boot delay issue, but I'd argue that "install a bootloader which can boot into the Windows installation" could be considered to cover it.

We don't have a test case in the matrix for this yet, but I did draft one, which never went into 'approved' state, probably just because I forgot about it:


I can re-propose that to the list and get it into the matrix for F17.

comment:3 Changed 5 years ago by adamwill

  • Status changed from assigned to closed
  • Resolution set to fixed

Well, I note we also have https://fedorahosted.org/fedora-qa/ticket/82 . As this ticket was ostensibly about the release criterion, let's close it as fixed, and use 82 to track updating / matrix inclusion of dual-boot test cases.

Note: See TracTickets for help on using tickets.