ECO/8.1.2/Checklist

From OLPC
< ECO‎ | 8.1.2
Revision as of 16:54, 12 August 2008 by Kimquirk (talk | contribs) (→‎Test)
Jump to navigation Jump to search

Release 8.1.2

Proposal/Review

This section should be completed by the Triage team.

USR Name: OLPC 8.1.2, OFW q2e12 
USR Target date: 7/30/08
USR wiki page: OLPC_SW-ECO_6
USR Champion: Richard Smith, Kim Quirk
Proposal approved: (date and Triage team signature)
___________________________________________________

Candidate build

This section should be completed by the build master.

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

---bootfw.i386 0:q2d16-1.olpc2.unsigned
+++bootfw.i386 0:q2e12-1.olpc2.unsigned

??? -- ???

---olpc-utils.i386 0:0.74-1.olpc2
+++olpc-utils.i386 0:0.74-2.olpc2

??? -- Install the failsafe low-space script.

---kernel.i586 0:2.6.22-20080523.1.olpc.28f4cb6e780db07
+++kernel.i586 0:2.6.22-20080808.olpc1.4c233ce8ed8f9cb

<trac>6532</trac> -- SD card corruption on suspend.

Test

This section should be completed by the QA lead.

Build tested:
Checklist
 Specific issue testing:            _x_ (NAND FULL test, on 709)
 1 hour smoke test:                 ___
 Fresh install:                     _x_  
 Upgrade testing:                   _x_  List builds tested from:708, 709 
 Downgrade testing:                 ___  List builds tested to:
 Tested on both B4 & MP:            ___
 Tested on multiple SKUs:           _X_  List SKUs: Spanish/English
 Tested on multiple keyboards:      _X__  List keyboards: Spanish/English
 Open, WEP, and WPA APs tested:     _X__  List brands, if appropriate: olpc, canopy
 New hardware tested, if supported: ___  C3 mother board
 Field testing, if possible:        ___

Release to signature/final test: (date and QA lead signature)
_Kimquirk 16:54, 12 August 2008 (UTC)__________________

Additional comments, if any:
 See Test_Group_Release_Notes for smoke test results.
 Tests/Journal/Nand-full
 Tests/Boot/Cleaninstall
 Tests/Boot/Security-Disabled

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): olpcrd-0.40-0
    Signed off by/date: ________________________________________

  Firmware/OFW version (/ofw/openprom/model; check against rpm -q bootfw): Q2E12
    Signed off by/date: Mitch Bradley, Wed Aug  6 05:43:43 UTC 2008

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

  Kernel version: (uname -r): 2.6.22-20080808.olpc1.4c233ce8ed8f9cb
    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 on the signed image.

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.