ECO/8.2.0/Checklist

This page lists the sign-offs required to advance through the 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.

ECO Name: ECO/8.2.0
ECO Target date: September, 2008 (slipped from August)
ECO Champion: Michael Stone
Proposal approved: (date and Triage team signature)
  March, 2008 --Michael Stone 22:16, 10 September 2008 (UTC)

Candidate build

This section should be completed by the build master.

Build number: 8.2-767
Firmware number: q2e18

Test

This section should be completed by the QA lead.

Build tested: 8.2-765
Checklist
 Specific issue testing:         Test_cases_8.2.0, TestResults_8.2.0
 1 hour smoke test:                ____
 Clean install:                    ____  
 Upgrade testing:                   ____  List builds tested from: 656, 703, 708, 760
 Downgrade testing:                 _n/a*__  List builds tested to:
 Tested on C2 and C3:               ____
 Tested on NiMH batteries:          ___
 Tested on en_US                    _**__    the degree of l10n/i18n for *'d keyboards and locales 
           es_*                     ___    will be considered by the release team in their judgements.
           mn_MN                    ___    
           ht_HT                    ___    
           fr_RW                    ___    note: while there are many Spanish and Arabic locales, 
           rw_RW                    ___    we don't yet distinguish between them.
           am_ET                    ___  
           ar_*                     ___
           kh_CA                    ___
           fa_AF                    ___
           hi_HI                    ___
           pt_BR                    ___
           ???                      ___
 Open, WEP, and WPA APs tested:     ___  List brands, if appropriate: in house APs
 Field testing, if possible:        ___

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

Additional comments, if any:

* there is no downgrade; you must cleaninstall to an older version
** See TestResults_8.2.0 for information on what keyboards were tested, and 
the test that was done. We didn't test languages or locales, just keyboards so 
I think this section should be changed to list the keyboards tested: 
 
 US/Intnl   ____
 Spanish    ____
 Arabic     ____
 Kreyol     ____
 Mongolian  ____
 Portuguese ____
 Thai       ____
 Amharic    ____
 Dari       ____

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.47-0.i386
    Signed off by/date: ________________________________________

  Firmware/OFW version (/ofw/openprom/model; check against rpm -q bootfw): CL1 Q2E18 Q2E
    Signed off by/date: ____Mitch Bradley, 2008-09-26_______

  Firmware/EC version: (/ofw/ec-name): PQ2E15
    Signed off by/date: _Rsmith 22:53, 17 September 2008 (UTC)

  Kernel version: (uname -r): 2.6.25-20080925.1.olpc.f10b654367d7065
    Signed off by/date: _____Deepak Saxena, 2009-09-26______

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)
_____________________________________________________________

Other signoffs

Upon or after announcement of the Signed Candidate:

 Documentation signoff:                ___     support lead
 Activities signoff:                   ___     build engineer
 Licensing signoff:                    ___     compliance consultant

The licensing signoff signifies that, to the best of the signatory's knowledge, "OLPC's compliance with its obligations under free software licenses is better in this release than in its previous most-compliant release."

One week after announcement of the Signed Candidate:

 One week of testing has elapsed:      ___     release team
 No untriaged bugs:                    ___     triage team
 No blocks:8.2.0 bugs:                 ___     triage team
 Release notes are approved:           ___     product management lead

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 ECO: (date and release team signature)
_____________________________________________________________

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