#6090 BLOC Update.: Document process of how firmware is built and released...

[Zarro Boogs per Child]

#6090: Document process of how firmware is built and released...
--------------------------+-------------------------------------------------
 Reporter:  jg            |       Owner:  wmb at firmworks.com
     Type:  defect        |      Status:  new              
 Priority:  blocker       |   Milestone:  Update.1         
Component:  build-system  |     Version:                   
 Keywords:                |    Verified:  0                
 Blocking:                |   Blockedby:                   
--------------------------+-------------------------------------------------
 The build process is already (mostly) captured in scripts that both Mitch
 and Richard are able to run, and is already mostly documented in
 http://wiki.laptop.org/go/Firmware_release_procedures which has been
 recently updated.

 We need to ensure the handoff to the base system build process itself get
 documented and how and when it versions unsigned and signed are pulled
 into test builds and release processes.  This is still being shaken down,
 so this should be ongoing work as part of Update.1's release.

 We are missing right now is a new naming convention for EC code, now that
 we have taken over EC responsibility from Quanta. we favor a separate
 number sequence for EC code, instead of trying to synchronize the EC name
 to the overall firmware release name.  The synchronization is always
 imperfect.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6090>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system