ECO/7.1.2/Checklist: Difference between revisions

From OLPC
< ECO‎ | 7.1.2
Jump to navigation Jump to search
m (Protected "OLPC SW-ECO 2 Checklist": Require signatures on checklist. [edit=autoconfirmed:move=autoconfirmed])
(No difference)

Revision as of 22:51, 17 January 2008

This page lists the sign-offs required to advance through the Unscheduled software release process for OLPC SW-ECO 2. Consult those pages for additional details on each step and sign-off.

Proposal/Review

This section should be completed by the Triage team.

USR Name: Ship2.2: Memory over-run; touchpad issues; include OFW
USR Target date: week of 2008-01-15 
USR wiki page: OLPC SW-ECO 2
USR Champion: C. Scott Ananian
Proposal approved: (date and Triage team signature)
_C. Scott Ananian, 17-Jan-08____________

Candidate build

This section should be completed by the build master.

Build number: ship.2-656
Packages added/changed/removed:
(each package diff should have a trac # and/or rationale)
  olpcrd 0.39 for trac #5317 (won't boot if NAND full)
  bootfw q2d07, no trac bug
  kernel 0:2.6.22-20071231.2.olpc.83e0631da83a269 for trac #2804 (jumpy mouse)

Test

This section should be completed by the QA lead.

Build tested:
Checklist
 Specific issue testing:            _P_
 1 hour smoke test:                 _P__
 Fresh install:                     _P__  
 Upgrade testing:                   _FB__  List builds tested from: 650, 653
 Downgrade testing:                 _FB__  List builds tested to: 653
 Tested on both B4 & MP:            _P__
 Tested on multiple SKUs:           _NA__  List SKUs: 
 Tested on multiple keyboards:      _P__  List keyboards: Urdu, Spanish, Portuguese
 Open, WEP, and WPA APs tested:     _NA__  List brands, if appropriate: 
 New hardware tested, if supported: _MP_
 Field testing, if possible:        _NA__

Release to signature/final test: (date and QA lead signature)
--Kimquirk 16:12, 17 January 2008 (EST) _________________________

Additional comments, if any:
  FB - waiting for final build to finish upgrade testing

Signature

This section should be completed by the security team.

Build to be signed: ship.2-656
Keys to be used:    MP
Security-critical components
  olpcrd version (rpm -q olpcrd): 0.39-0
    Signed off by/date: _C. Scott Ananian, 2008-01-17__
    Md5sum of data.img inside rd.zip: 9c29028caecd7fff709bf8540a2f417f
    Comments: no security-relevant changes since 0.37, signed in 653.

  Firmware/OFW version (/ofw/openprom/model; check against rpm -q bootfw): q2d07-0
    Md5sum: 6ea9b4d7e66cef93603919a8191d3011
    Signed off by/date: __Mitch Bradley, 2008-01-17___

  Firmware/EC version: (/ofw/ec-name):
    (Should be same md5 as OFW above.)
    Signed off by/date: __Richard Smith, 2008-01-17___

  Kernel version: (uname -r): 2.6.22-20071231.2.olpc.83e0631da83a269
    Md5sum of data.img inside os.zip: ebf749585facb02b9cbc8921fbe528a4
    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.