+-----------------------------------------------------------------------------+ | * This is the process of release testing as things currently stand. | | * Treats compose process as an external process, handled by releng. | | * "Fedora n" is a generic way of saying the newest stable release of Fedora | | * A milestone is one of alpha, beta or final | | * Dotted lines indicate a manual task | | * Normal lines indicate an automated task | +-----------------------------------------------------------------------------+ +---------------------------------------+ | Fedora n+1 is branched from rawhide | | | +---------------------------------------+ | v +---------------------------------------+ | Packaging and/or Metadata Changes | | Are Applied to Fedora Branched |<------------------------------------------------------------------------------.<--------------. +---------------------------------------+ | | | | | <----------------------------------------------------------------------------------------------. | | | | | | v | | | +---------------------------------------------------+ | | | | Fedora branched is composed on a daily basis | | | | | | | | | +---------------------------------------------------+ | | | | | | | v +----------------------------------------------------+ | | | /--------------------------\ | QA and Releng work together to find the root cause | | | | | Did the compose succeed? |-------------------->| of the compose failure and coordinate a fix with | | | | \--------------------------/ No | affected package PoCs | | | | | +----------------------------------------------------+ | | | Yes v | | | | +----------------+ | | | | .-----------------------------------------------| Start Testing! | | | | | v +----------------+ | | | | +---------------------------------------------------+ | v | | | | OpenQA sees a fedmsg signifying that the compose | | +-----------------------------------------------------+ | | | | has completed and schedules a battery of tests | | | The appropriate fix is applied so that the next | | | | +---------------------------------------------------+ v | compose will pick it up |-----' | | | /-------------------------\ +-----------------------------------------------------+ | | v | Should this compose get | | | +---------------------------------------------------+ | more human testing? |------------------------------------------. | | | OpenQA tests execute on the compose, emitting a | \-------------------------/ Yes | | | | fedmsg when each test completes | | | | +---------------------------------------------------+ | | | | v | | v +----------------------------------------------+ | | +---------------------------------------------------+ | A nightly compose is submitted to QA for | | | | Another daemon picks up the "OpenQA Job Complete" | | more in-depth testing | | | | fedmsg and translates those results in OpenQA to | +----------------------------------------------+ | | | passes in the matrices (if appropriate and if the | | | | | test did pass at least once) | | | +---------------------+ +---------------------------------------------------+ | | | Increment Milestone | | v | +---------------------+ | +--------------+ +----------------------------------------------+ | ^ | Report Results To | Fedora Wiki | Report Results To | Testers run through the test cases indicated | | | '----------------------------------------------->| {s} |<-----------------------| in the release validation matrices | | | +--------------+ +----------------------------------------------+ | | | | | | | | '--------------------------------------------------------. | | | | | v | | +-------------------+ | | | Go/No-Go Meeting | | | +-------------------+ | | | | | v | | /--------------------------------------\ | | Yes | No blocking failures in the test | No +----------------------+ | .--------------------------| case matrix and all accepted blocker |---------->| Slip release 1 week | | | | bugs have been handled | +----------------------+ | | \--------------------------------------/ | | | | | | | | | v | +----------------------------+ /-------------------------------\ No | | Milestone Release Complete |----------->| Is this the final milestone? |-----------------------------------------' +----------------------------+ \-------------------------------/ | | Yes | v +----------------------------+ | SWEET, SWEET VICTORY!!!!! | +----------------------------+