USR Checklist: Difference between revisions

From OLPC
Jump to navigation Jump to search
(First version of USR checklist.)
 
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<b><big><font color=red>For current information on OLPC software release processes, see [[Release Process Home]]</font></big></b>

{{Deprecated}}

This page lists the sign-offs required to advance through the [[Unscheduled software release process]]. Consult that page for additional details on each step and sign-off.
This page lists the sign-offs required to advance through the [[Unscheduled software release process]]. Consult that page for additional details on each step and sign-off.


==Proposal/Review==
==Proposal/Review==
''This section should be completed by the Triage team.''
''This section should be completed by the Triage team.''
ECO Name:
USR Name:
ECO Target date:
USR Target date:
ECO wiki page:
USR wiki page:
USR Champion:
Proposal approved: (date and Triage team signature)
Proposal approved: (date and Triage team signature)
___________________________________________________
___________________________________________________
Line 24: Line 29:
Upgrade testing: ___ List builds tested from:
Upgrade testing: ___ List builds tested from:
Downgrade testing: ___ List builds tested to:
Downgrade testing: ___ List builds tested to:
Tested on both B4 & MP: ___
Tested on C2 and C3: ___
Tested on multiple SKUs: ___ List SKUs:
Tested on NiMH batteries: ___
Tested on multiple keyboards: ___ List keyboards:
Tested on Intl English keyboard: ___
Tested on Spanish keyboard: ___
Tested on other keyboards: ___ List keyboards:
Open, WEP, and WPA APs tested: ___ List brands, if appropriate:
New hardware tested, if supported: ___
New hardware tested, if supported: ___
Field testing, if possible: ___
Field testing, if possible: ___
Line 40: Line 48:
Keys to be used:
Keys to be used:
Security-critical components
Security-critical components
olpcrd version (rpm -qi olpcrd):
olpcrd version (rpm -q olpcrd):
Signed off by/date: ________________________________________
Signed off by/date: ________________________________________
Firmware/OFW version (/ofw/openprom/model):
Firmware/OFW version (/ofw/openprom/model; check against rpm -q bootfw):
Signed off by/date: ________________________________________
Signed off by/date: ________________________________________
Line 78: Line 86:


''This section should be completed by the release team.''
''This section should be completed by the release team.''
Approved build number:
Release team final sign off on USR: (data and release team signature)
OS version:
Firmware/OFW version:
Firmware/EC version:
Wireless firmware version:
Champion sign off: (date and champion signature)
_____________________________________________________________
_____________________________________________________________


Release team final sign off on USR: (date and release team signature)
Given two signatures above, the USR build can be published as official.
_____________________________________________________________

Given three signatures above, the USR build can be published as official.

[[Category:Procedures]]

Latest revision as of 17:08, 8 February 2011

For current information on OLPC software release processes, see Release Process Home

Stop hand.png WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.

This page lists the sign-offs required to advance through the Unscheduled software release process. Consult that page for additional details on each step and sign-off.

Proposal/Review

This section should be completed by the Triage team.

USR Name:
USR Target date:
USR wiki page:
USR Champion:
Proposal approved: (date and Triage team signature)
___________________________________________________

Candidate build

This section should be completed by the build master.

Build number:
Packages added/changed/removed:
(each package diff should have a trac # and/or rationale)

Test

This section should be completed by the QA lead.

Build tested:
Checklist
 Specific issue testing:            ___
 1 hour smoke test:                 ___
 Fresh install:                     ___  
 Upgrade testing:                   ___  List builds tested from:
 Downgrade testing:                 ___  List builds tested to:
 Tested on C2 and C3:               ___
 Tested on NiMH batteries:          ___
 Tested on Intl English keyboard:   ___
 Tested on Spanish keyboard:        ___
 Tested on other keyboards:         ___  List keyboards:
 Open, WEP, and WPA APs tested:     ___  List brands, if appropriate:
 New hardware tested, if supported: ___
 Field testing, if possible:        ___

Release to signature/final test: (date and QA lead signature)
_____________________________________________________________

Additional comments, if any:

Signature

This section should be completed by the security team.

Build to be signed:
Keys to be used:
Security-critical components
  olpcrd version (rpm -q olpcrd):
    Signed off by/date: ________________________________________

  Firmware/OFW version (/ofw/openprom/model; check against rpm -q bootfw):
    Signed off by/date: ________________________________________

  Firmware/EC version: (/ofw/ec-name):
    Signed off by/date: ________________________________________

  Kernel version: (uname -r):
    Signed off by/date: ________________________________________

Signatures above certify that, to the best of your knowledge, the above components are at least as secure as other components signed with these keys.

This section should be completed by the build engineer.

Checklist
 Appropriate sign-offs present above:          ___
 Versions in build match those approved above: ___
 QA lead sign-off under 'Test' above:          ___
 Packages in build match those expected:       ___

Checklist sign-off: (date and build master signature)
_____________________________________________________________

Final test

This section should be completed by the QA lead.

Build tested:
Checklist
 1 hour smoke test:                    ___ (catch signature process regressions)
 USB stick fresh install on wp laptop: ___
 USB stick upgrade on wp laptop:       ___
 Network upgrade on wp:                ___
 Other testing (describe):

Sign-off for release: (date and QA lead signature)
_____________________________________________________________

This section should be completed by the release team.

Approved build number:
OS version:
Firmware/OFW version:
Firmware/EC version:
Wireless firmware version:

Champion sign off: (date and champion signature)
_____________________________________________________________
Release team final sign off on USR: (date and release team signature)
_____________________________________________________________

Given three signatures above, the USR build can be published as official.