Regressions will be run periodically by QE, in order to ensure that everything is functional. This should be done before every release, including new builds of previous releases. Nothing should be delivered to customers that QE hasn't run a regression on and signed off on.
Red Had developers will do initial validation as part of delivery. Red Hat QE will do verification to ensure everything works correctly, before delivering to customer.
They are responsible for testing. Test strategy should be reviewed before it is merged.
In order to maintain a high level of quality upstream, Red Hat developers will make a point of fixing any bugs raised in upstream PTP project. While priority may be given based on business requirements, as maintainers of the upstream PTP project, Red Hat developers will eventually fix all legitimate upstream bugs, regardless of who raises it. However, other partners and contributors to the upstream project will be strongly encouraged to fix bugs too, especially those that they raise or are primarily impacted by.
Any bugs raised by customers should be given priority in investigation. Red Hat developers will follow these steps when addressing bugs:
- Determine whether the behaviour the customer describes is intended
- If behaving as intended, inform customer
- If customer pushes issue, they can raise with Red Hat business team
- If so, determine whether this is a user error causing this to occur, If user error, inform customer of what they’re doing incorrect
- If a legitimate issue, determine whether this has been fixed already in later release If so, backport
- If not fixed yet, determine if reproducible upstream
- If reproducible upstream, fix upstream and backport
- If not reproducible upstream, was it unintentionally fixed?
- If so, backport
- If not, find where it was introduced through cherry pick and handle appropriately.