SosreportUpdates
|
Size: 2555
Comment:
|
Size: 2244
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| This is the mandatory QA process that the proposed packages have to pass. We will split it into two sections: code QA and package QA. === Code QA === The objective of the code QA is to make sure that the code changes fix or implement what they intended and have no ill side effects. The following requirements must be met: * each change needs to have a Launchpad ticket filed under the landscape-client project * each one of those tickets needs to have: |
This is the mandatory QA process that the proposed packages have to pass. The following requirements must be met: * each change must have a Launchpad ticket filed under the landscape-client project * each one of those tickets must have: |
| Line 18: | Line 13: |
| * self tests must all pass (already a standard Landscape coding practice) | * all self tests must pass (already a standard Landscape coding practice) * after the upgrade, the client must still be able to talk to the Landscape server The above tests exercise the code changes. The packaging changes need an extra QA procedure outlined below. |
| Line 25: | Line 22: |
| The following requirements must be met: * each packaging change must have a Launchpad ticket filed under the landscape-client ubuntu package * each one of those tickets must have: * two developer reviews (already a standard Landscape coding practice) * a specific QA review The resulting package, with all the changes in place, needs to undergo the following additional QA procedures: |
The resulting package, with all the changes in place, must undergo and pass the following additional QA procedures: |
DRAFT, DO NOT COMMENT ABOUT THIS YET - Andreas - Jan/2008
This document describes the policy for updating Landscape client packages in a stable supported distro, be it LTS or not.
Landscape is a commercial service from Canonical which periodically offers new features to its customers. Being a client-server product, the client part needs to be periodically updated in order to take advantage of the new features. Therefore, new features are allowed in an update as long as the conditions outlined below are met.
QA Process
This is the mandatory QA process that the proposed packages have to pass. The following requirements must be met:
- each change must have a Launchpad ticket filed under the landscape-client project
- each one of those tickets must have:
- two developer reviews (already a standard Landscape coding practice)
- a specific QA review
- all self tests must pass (already a standard Landscape coding practice)
- after the upgrade, the client must still be able to talk to the Landscape server
The above tests exercise the code changes. The packaging changes need an extra QA procedure outlined below.
Packaging QA
The objective of the separate packaging QA is to test:
- package upgrades
- package installation from scratch
- distribution upgrade
The resulting package, with all the changes in place, must undergo and pass the following additional QA procedures:
- upgrade test from previous distribution to the current one. If the current distribution is an LTS one, the upgrade path from the previous LTS distro must also be exercised. This upgrade test must be performed using do-release-upgrade
- upgrade test from previous version of the package. This test must be performed with:
- dpkg
- apt-get install/upgrade
- smart install/upgrade
- using the Landscape service itself
- installation from scratch in the current distribution:
- using dpkg
- using apt-get
- using smart
- optionally, because of the added complexity and because the author of this document is not yet sure how to do it, the installer of the current distribution should also be tested using the new package to make sure it works in the installer environment
SosreportUpdates (last edited 2023-12-06 15:53:39 by yanisa-hs)