Ticket #85 (closed enhancement: fixed)

Opened 7 years ago

Last modified 6 years ago

Clarify wiki test priority

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



There was some confusing around the priority listed in the install and desktop test matrices. The question was, why do we give the go decision to release, even when there are test failures from tests with a matching release level?


Adam pointed out that this is because the bugs exposed caused the test to 'fail', but don't really break the underlying release criteria. I think we could perhaps track this type of 'failure' specifically in the results tables).

enhancement recommendation

I think this is a messaging/education issue. Perhaps we just need to clarify that the priority listed is the test execution priority. It does not always mean that a failure identified by those tests will block the applicable release.

Updates or adjustments may be needed to the https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event or to the Fedora 14 test results template (when available -- https://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template).

Change History

comment:1 Changed 6 years ago by jlaska

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

Not sure what else to do to resolve this issue. I believe the updated test event summaries that go out clarify how bugs found impact the release criteria. I'm closing this ticket out. Feel free to re-open if there are any additional work items I've missed.

Note: See TracTickets for help on using tickets.