#5589 BLOC Update.: Ensure up to date firmware is in Joyride and then update.1

[Zarro Boogs per Child]

#5589: Ensure up to date firmware is in Joyride and then update.1
----------------------------+-----------------------------------------------
  Reporter:  jg             |       Owner:  jg                      
      Type:  defect         |      Status:  new                     
  Priority:  blocker        |   Milestone:  Update.1                
 Component:  new component  |     Version:                          
Resolution:                 |    Keywords:  dgilmore, cscott, rsmith
  Verified:  0              |  
----------------------------+-----------------------------------------------
Changes (by wmb at firmworks.com):

  * owner:  wmb at firmworks.com => jg
  * component:  ofw - open firmware => new component


Comment:

 See also #5565 .  That ticket suggests that a management policy decision
 is a necessary part of this discussion.

 The firmware release process puts the image in e.g.

   http://dev.laptop.org/pub/firmware/q2d07/q2d07.rom
   http://dev.laptop.org/pub/firmware/q2d07/q2d07.rom.md5

 Scripts can find the latest released version by inspecting the symlink:

   http://dev.laptop.org/pub/firmware/LATEST

 The image contains an embedded build timestamp and an embedded CRC.  It is
 important that all copies of a given released version be bitwise
 identical, so it is not feasible to rebuild a second copy from source for
 the purposes of including a copy in the OS image.  The procedure should be
 to get a copy of the released bits, verify the md5sum, sign to create a
 bootfw.zip, and then package for inclusion in the OS build.

 I am insufficiently familiar with the processes and tools involved in the
 OS building process to give further details.

 Having begun the discussion by describing the part of the process that is
 under my control and outlining the other parts, I am reassigning this to
 "new component" and changing the owner back to jg.  I suggest that we
 create a new component named "release" and then change this ticket's
 component to that.  The final solution of this issue lies in the release
 engineering domain, not in the ofw domain.

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